LeapIn.it uses a REST endpoint for access to the database. This is a design pattern for hypermedia systems, which advocates providing individual resources (e.g., people) with unique URLs, and using those URLs to exchange structured information. HTTP requests can be made to these URLs, where HTTP methods are used to instruct what should happen with attached data, and status codes… Read more →
Team Orion has now designed and implemented a prototype of Leapin.it. This post will conclude the project by describing the process we have been through, followed by the future possibilities of LeapIn.it. Overview LeapIn.it was not one of our original ideas – it formed from the development of an idea on gaming, and a focus on virtual worlds within gaming…. Read more →
LeapIn.it uses a REST endpoint for access to the database. This is a design pattern for hypermedia systems, which advocates providing individual resources (e.g., people) with unique URLs, and using those URLs to exchange structured information. HTTP requests can be made to these URLs, where HTTP methods are used to instruct what should happen with attached data, and status codes… Read more →
The code for the prototype is available to download from our GitHub repository.
This post will give a brief overview of how we plan to market LeapIn.it and how we plan to pitch it to investors. Marketing We have planned to produce some video advertising, which will appear on video streaming website, TV and motion billboards. This will consist of a series of adverts which demonstrate the use of LeapIn.it in different situations…. Read more →
Throughout implementing the prototypes, we’ve employed a number of testing methodologies to ensure that the product is of a high quality. In this post, we’ll discuss four methodologies we have used: regression testing, code modularity, code quality checking and code metric monitoring. Regression testing After each significant change was made to the code, the prototype would be compiled into an… Read more →
During our development of the LeapIn.it prototype, we have used a number of design patterns, libraries and API’s. This post will give an overview of the most crucial of these. Server The server is responsible for creating a REST interface for database access. As mentioned in our post on architecture, we have chosen to use RedBeanPHP to communicate with the… Read more →
The purpose of this post is to present the outcomes of the usability evaluation study which is described here. The study consisted of a survey, which was completed the critical friends Michael Day, Faranak Hardcastle and Laura Hyrjak. The standard interface This section of the study was designed to evaluate the standard linear interface, as described here. Advantages: Michael Day… Read more →
With a prototype now implemented, our critical friends will now evaluate it, giving particular attention to the usability. We will provide them with a instructions on areas of the system they should test, and what they should observe. This is split into three parts: interface comparison, general interface evaluation and concept evaluation. Interface comparison The participants are given two links… Read more →
We have now implemented a prototype with most of the features we discussed in the design. The following video gives a demonstration of this prototype: This prototype is available here (use the username “test” and password “test”). Screenshots [portfolio_slideshow] Note: the names of rooms and users are chosen randomly by implementing a random words generator.
