How I do love quick, A4 ‘mock-ups’ (if you can call it that). Anyway, have been thinking about the necessity of a website and what it would bring to the project. My gut feeling is that it should be there, however, I’m wondering if I’m only saying that because websites are my comfort food; I can build a website quickly and without too much effort.

Assuming I do include a website as part of the project then I’ve decided it should have the following features/characteristics; by no means a final list but I do intend to keep features down and generally follow the K.I.S.S rule of thumb.

Website features:

• Account system; create a unique id for identifying yourself on the slopes and for associating your videos with your account.
• Access saved video from previous runs.
• get weather reports, lift status, etc from all participating resorts (defaults to preferred resort based on account pref. or nearest resort from determining user location).
• (extra?) Calendar of events for resorts.
• (extra?) Photos/video/reports of above events.
• Store for purchasing lift passes, saved video, etc.

Characteristics

• Profiles are, by default, private but content can be made public if desired (e.g: to share with friends).
• Users can view, rate and discuss video uploded via the system (would require content/users to declare content public).
• Feel of the site is simplicity, not over packed with features. Highly focused on the video angle and not so much on other aspects of the sport (i.e no discussion forums).

To summarise, a website would be a nice feature but for the degree show (and grading) I would like to focus on getting the iPhone - camera system working then, if time permits, build a website. Regardless of what is physically created the concept incorporates a website but it may be that a website is mocked come grading - I will likely be able to build a site in time for the Degree Show.