The following checklist outlines the features that were aimed to be completed during prototyping. The green objects were successfully completed, the orange objects are incomplete:
- Train routes & stations
- Scaleable vector graphics
- Replicate touch interface with click & drag interactivity
- Search by station function
- Functioning QR code generation and scanning
- Dynamic route tracing using vector graphics
- Responsive buttons and text (consistent size regardless of resolution)
- Functioning journey planning algorithm (partially accurate)
- Twitter feed
- Mobile design
For ideal viewing, please take the following into consideration:
- Prototyped largely using Firefox (ideal browsing platform)
- Responsive design for any aspect ratio, but tall (5:8) preferrable
- This is a prototype for a touch interface on a non-existant device, so for the sake of the prototype, the cursor is intended to replicate the user's finger
- Click and drag in the empty space to move around the viewport.
- Click and hold on a start location, drag your mouse over a destination, and release mouse click.
- Click the QR code generator to bring up a functioning QR code. Scan the QR code with your mobile device to retrieve your current journey plan on your phone.
- On trips where you must exchange services, the algorithm may return a journey that is not possible to make before the first service arrives at the station.
- Blank schedule may be displayed at times (rare).
- CSS not 100% functioning across all platforms, can result in styling problems (e.g. offset logos)
- Twitter feed can stretch out of div if too long
- QR code doesn't always generate in the center of the window
- Mouse functions don't work on mobile devices. This is okay because mobile platforms were always intended as journey viewers, not interactive planners. However, the current implementation of that concept wasn't intentional.