featured_spectre Posted May 10, 2010 Posted May 10, 2010 Application Fundamentals | Android Developers Seems to cover the basics for what we need. It would also appear that most of the code is a hash of XML, VBS and PHP
LosOjos Posted May 11, 2010 Posted May 11, 2010 Haven't got the link at the moment, but Google Droid Draw, it's a visual app designer that generates the necessary XML for the form you design
localzuk Posted May 12, 2010 Posted May 12, 2010 I think the first thing we need to do is decide what the future API for connecting to the website backend will contain. Once we have an API planned (and whether or not the implementation is finished) we can then move on to some form of interface planning (I'm currently playing with SketchFlow in Expression Blend so as to knock up a basic interface design idea or 2), and then from that we could look at creating apps for the various platforms - dependant on who feels strongest with which platform/language. Personally, I'm thinking that keeping the apps as similar as possible would be a good idea - that way there's no arguing over why one platform has a feature that another doesn't etc... Thoughts?
featured_spectre Posted May 12, 2010 Author Posted May 12, 2010 well C# (for Apple products) or a combination of C# and Java (for Droid/WP7) would be the obvious choice. The best way to get them similar is to design the interface first, then duplicate it as required and code up for each specific one. That way the interfaces can be identical, but the backend suits the needs for the phones.
Recommended Posts