...
This part of the project took a fair amount of work, but we were happy with the results. We were able to produce a usable interface suitable for heuristic evaluation. Starting work earlier could have made the process less stressful.
On the technical side, we We used the jQuery Mobile framework, which was helpful in building the interface quickly. It However we had performance issues , so we had to make a brief detour that forced us to replace it with Twitter Bootstrap before starting on GR5's backend. The lesson we learned is that jQuery Mobile can help prototypeis great for prototyping, but is not currently suitable in its current state for final interfaces, and . We also learned that you don't necessarily need a framework specifically for mobile HTML - . Twitter Bootstrap worked finewell for our application, and is general purpose.
...
Our final implementation reached relative feature-completeness, incorporating live data from all four of our intended information sources. We didn't get have time to implement the "Share" feature because of time constraints (, but it was a non-essential task). Starting earlier might have enabled us to get to it. We may have taken the time constraint too likely and not prioritized well enough - on a couple of occasions we fixed cosmetic/smaller issues when major tasks should have gotten more attention. In a future project, a better approach would be to completely handle all issues with major tasks before moving on to minor ones.We could have managed our time more wisely by prioritizing tasks and completing more important tasks first. However, there was simply bad timing for our group for GR5--one group member was out of town attending CHI, and another had a paper deadline around the same time as the GR5 deadline.
Switching We think switching from jQuery Mobile to Twitter Bootstrap was the right move - the interface was made our application much more responsive, and actually simplified the code actually got simpler in places!