It's never just the code!
They say "techies" never really believe this. All they supposedly want to do is to write the greatest code, and
voila! everybody takes up the product.
This theory of it's not just being the code came to the fore in our technical meeting. We met to discuss the development of our prototype. And it turned out to be a mixture of the technical, and other factors such as time (how much time is left in the class), strategy, the target of the end product, etc.
I haven't done much (if any) of mobile systems development but the same principles of architecting a system applied. Using our "Use Cases", we developed a flow for the application, and then translated this to a very high level pseudecode. This makes it much easier to write the actual code, especially since we'll be working with new components none of us on the development team have used before.
Things are moving forward, step by step.