using the Google App ecosystem has the benefit of extending Teamwork's potential uses -AND- preserves the zero IT footprint proposition (if Teamwork is implemented as SaaS. - a market winner especially for smaller company adoption of Teamwork!).

would help to make Teamwork much more versatile - thanks development team

I agree with Brian - in the North American "non-consumer" market, defacto platform standards are important, as evidenced by Wintel domination of the PC-based client/server architecture. But the next decade may see the mobile architectures overshadow the all enterprise IT that exists today (it seems inevitable in raw number terms). Here the iOS platform (iPhone-to-iPad) is mostly considered a consumer platform which leaves Android as the other 'hot' platform and is seemingly more IT-like (lots-o-development appeal/options/etc.). From all this admittedly unscientific empirical evidence, I'd advocate for an early priority to be given to the Android platform over iPhone for Teamwork's likely users?!?!?! - (sorry Blackberry and WebOS users - a famous hockey player once said "you have to skate to where the puck is "going to be," not where it is now!)