In the case of LANT, there are so many features that require a working intranet server and/or a large userbase to generate statistics, the early prototype/mock-up/simulation focuses on just offering an insight into the interactive side of LANT and demonstrating how it will integrate with Windows.
The LANT prototype was developed in Adobe Flash and uses the versatility of that format to try and offer the best ‘simulation’ possible. The task that was most daunting in developing this prototype was creating an authentic Windows-style Operating System mock-up, so that users of the prototype would be immersed enough to think they were using their own PC.
To do this I used a Windows Vista style glossed look in the regular mode, and carried on the made-up “Big LAN 2008” theme in the LAN mode. I believe these themes give enough contrast to each other that users of the prototype will appreciate how different the use of a computer is at a LAN Party compared with regular use.
Unfortunately, because of the limitations of a simulated, mock-up style prototype in Flash, the ‘Community’ features (Intranet functionality) would be unfeasible to recreate in this prototype. This is because an external server and several workstations would be needed to offer a reasonable set of statistics to display, and a method to display them.
Overall the prototype gives the user a basic insight into the main functionality of LANT (keeping different PC uses separate), and definitely achieves what it is intended to do.
Design Evaluation
In some regards the design of LANT was the project’s most crucial step. This is because the design would have to justify itself to a regular audience as to why it is being designed for a more niche target group (LANners and developers).
The design adequately gave enough insight into what LANT was intended for and why it would be successful, however did not give much insight into its target audience. The target audience are primarily experienced PC users, that have the knowledge to game and attend LAN parties. The audience also usually want to attend these events and realise it is a large operation (comparable, for example, to going on holiday and having to prepare and pack luggage). It is from this understanding that LANT was thought up as a simple, free, and open source solution to the software problems that arise from attending a LAN event.
In order to test if the design was welcomed by the target crowd, a basic HTML mock-up that showed what options would be available on the options screen and how the two modes of operation would differ from each other, but offer limited interactivity, was made and published on the Internet. (http://zappa.tvu.ac.uk/~06hodgsonbyrnew/mockupHTML)
The feedback on this mock-up from members of this target audience was phenomenal, every user tested was excited about the idea and even suggested new proposals for the project, such as LANT merchandise to be available from popular “Geek” shops (such as www.thinkgeek.com). This merchandise included having a physical button to press to switch modes, dubbed “The Emergency LAN Button”, which would also generate some revenue to the LANT project. This adds credibility to the point made that “LANners” (as they often refer to themselves as), are a good source of developers, and because LANT would be open source, it would be an easy platform for them to develop for.
A user that also tested LANT compared it to have the same revolutionary elements of Valve’s hugely successful ‘Steam’ platform. Steam is an online game distribution and community service that revolutionised the way many PC gamers play their games.
Steam essentially was the first program to offer what it does, and is still considered the only program to offer this function well even though other companies (even huge corporations such as EA Games) have released similar software.
Overall after approaching users in the target audience, the design for LANT was well informed and reflected what the users wanted, and so the idea was definitely worth pursuing.
Proposal Evaluation
The proposal was a very sketchy stage of LANT as it was making huge assumptions about what the program would do and who it would do it for.
The original proposal put forward a very vague idea of a “customizable advanced desktop virtualization software”. This idea did not have much ambition to it, and would not have received as much of an enthusiastic praise as it has if it had stayed at this stage.
The catalyst that really drove LANT to become ambitious (and still feasible) as it has become was the theory of making a LAN Party a “Community”, and advancing pre-existing software to new levels using LANT’s Intranet feature.
This feature added a new zest to the project that took the design process in a whole new direction.
The proposal for LANT had to stand up to a lot of criticism from non-LANning peers, which was unexpected at this stage, but in later stages where the target audience appeared to be much more of a niche crowd, it was anticipated.
Because of the criticism received on this proposal, more visuals had to be used in the design process, to fix the flaw in the proposal: that it was mostly text, describing a visual process.
The majority of technical details about LANT were covered in the proposal, such as what systems it would be implemented on, how it could be implemented etc. Later on these details would become usability issues rather than technical ones. For example the fact that LANT would only be available on Windows systems, is not a technical issue in later steps, it becomes an issue of demand, as the target audience predominantly use Windows-based PCs.
Another step not majorly focused on in the proposal, but then proved to be popular (even with non-LANning peers) in later stages when it was described and shown in more detail, was the Overlay feature. This feature and the Intranet feature are quite similar in function, the only difference is that the Overlay is intended to display computer stats that are a lot more personal to the user, whereas the Intranet stats are ones that the user wishes to show off to their ‘LAN Community’.
Overall the proposal was not a good stage in the LANT project, as it didn’t describe itself enough to get peers to understand it. Luckily, this problem was corrected in the design and prototype stages.
Possible Improvements
Below the possible improvements that could be made to the development stages of LANT will be listed...
Proposal
The proposal started off the project enough, but not as well as would have been desired. It would have benefitted the proposal better if more images of LANT mock-up screens or sketches were included, so it didn’t have to explain itself through text.
This also goes for its references and inspirations. The proposal would not have received as much criticism from peers as it did if it had included pictures and videos of other desktop virtualisation software, Intranet software or actual LAN Parties.
Design
The design was the turning point in the project and so not much needs to be improved upon. However, there is an item that could be looked at though, which is how the project was researched at this stage. The actual ‘market research’ was at a stage between Designing and Prototyping, where the mock-ups were used to create an HTML page. Time would’ve been saved if the still mock-up images were used and demonstrated to the target audience instead of letting them figure out how to use LANT on their own remotely. This would have skipped the “in-between” stage of the HTML mock-up and left time to advance the Flash prototype more.
Prototype
The prototype is a very successful, interactive mock-up that does what it is intended to do. However, there is still room for improvement...
- Use a genuine adaptable full-screen script, so that whatever size monitor the prototype is executed on, the screen looks like it would be running in the system’s set resolution.
- Use real-time stats from the host system, so for example when the prototype is opened, the system clock on the prototype would use the host system’s system time.
- Use more advanced frame code, so that windows stay open/closed when switching modes or minimizing/maximizing as they do in real operating systems.
- Use a right click and double click script for the system tray icon, so as described in the design, when the tray icon is double clicked LANT switches modes, and when right clicked it bring up the LANT menu.
- Incorporate simulated test data, so a mock-up Intranet webpage would be accessible in the prototype.
- Add a more detailed help index and documentation, on top of having the current ‘Tip’ popup bubble.
- A real LANT webpage, where you can download the LANT prototype.
These are not vital in this stage of development, but would be necessary if the project was going to be developed into a final piece of software.
