Google Android Platform - The Android Log

An interesting thread started in the Google Android Developers group, why hasn’t Google provided a User Interface Guide for Android? Is it up to the Android community to write these type of documents? Until recently, Free-Software has not had a celebrated history of creating outstanding GUI experiences. What will the Android experience be like if every developer has their own way of presenting user information and menu choices?

It can be a serious challenge to get hobyists and part-time free-software developers to devote precious time to the creation of style-guides and interface documents. Plus, how would a hobyist Android developer find a testing environment to study user interaction and gather feedback?

For at least six years, companies including Sun and Novell have invested heavily in improving the usability of the Gnome User Interface. The leaps and bounds that the Gnome UI has made since then is very impressive but it took money from large, established companies to create standards guides, provide testing labs and quality-control specialists. In 2001, Linux Weekly News interviewed Calum Benson about the work he was doing as a Sun employee working on the Gnome Usability Group in it’s early days.

The other critical thing is to ensure you don’t *have* to know about all the ways of doing something to complete the whole task. This problem showed up in the study with respect to panel customization, and especially fonts– there’s no one place in GNOME 1.4 to change all the fonts on your desktop, you have to know at least three different places to go.

So yes, it’s important that the key features on a desktop are well signposted, especially if you’re new to that particular environment. But while more advanced features or quicker ways of doing the same thing may not become apparent until you reach a higher level of competence and start experimenting and exploring, they still need to be designed to be
as easy to use as possible.

What kind of documentation is Android missing? Here is a small sample of similar user-interface documents that Microsoft provides independent Windows Mobile application developers.

• Accessibility and Ergonomic Guidelines - Outlines the guidelines for developing an accessible user interface.
• Home and Today Screen Guidelines - Describes the information the user might want instant access to, and ways to display it when the component is selected.
• Mobile Web Site Design Overview - Some general guidelines on how to optimize your Web site design for Internet Explorer Mobile.
• Navigation Guidelines - Describes the various views (list view, summary view, and edit view). and provides recommendations for using them.
• Screen Rotation Guidelines - Describes practical approaches you can take to create screen layouts that accommodate portrait, landscape, and square.
• Soft Key and Menu Guidelines - Describes the role that Soft Keys play in the user interface, and how to properly implement them in your applications.
• Usability Guidelines - Provides a checklist to help you confirm that your application’s user interface meets usability requirements.
• User Interface Control Guidelines - Provides guidelines for user interface (UI) controls.
• User Interface Text Guidelines - Provides guidelines for designing user interface text.

What do you think? Is this a deal-breaker for your mobile applications or is it a non-issue? 

Technorati Tags: Google, Android, User-Interface, Microsoft, Windows Mobile, Apple, Design, Guides

An interesting thread started on the Android Developers Google Group this week. Kev started the conversation by questioning how other developers felt was the best method to create a product that provides some revenue.

If we develop a handy utility or game or whatever to run on Android what is the intention for the business model for this:

• Is the idea that it is all just a free-for-all?
• Are we expected to make our own arrangements to sell the app from our sites or Handango or whatever?
• Is there going to be some market place where users can pick and choose the apps?
• Is there going to be some mechanism for promoting apps to users?
• Are there going to be bus dev people for us developers who will help get apps built into Android devices as they are shipped?
• How can we protect our apps from piracy?
• If our app gets popular will Google buy us?

Any other guidance as to what to expect would be great.

What followed was some great discussion, with one of the best responses coming from 3Dwulf:

Excellent question, most people are probably hoping to get the development in so that Google blesses their work with some prize money and recognition and/or a gig for the team. Developing applications should have some type of business model in mind (say a subscription, free application but pay-for-premium plug-ins, etc.).

Admittedly, some type of commerce functionality should be a by-product of what-ever application that is developed. It is hard to be truly altruistic and create the absolute best application for this platform and at the same time try to figure how to extract cash from the customers that will use it in the first place.

The major players, Google, the Service Providers and the Media corporations have got their ducks in a row and are in the best
position in this race to win with the cash in their coffers. They are betting that the developers (which they do not initially have to hire), will provide them with the next big cash cow, when it does start gaining momentum after the application has been developed and gained the proof of concept they are looking for, then, and only then, will the powers that be consider placing their bets.

Any team of developers should consider this the new business model of the times after all why take risks hiring developers to develop applications that have not been market tested, when all the power players have to do is sit and wait for *all* the works to come to fruition and then put the carrot on the stick for the asses to follow.

My advise is two-fold, build the application *with* a business plan in mind from the beginning so when the Devil wants to negotiate one will have more leverage in the negotiating process.

View the entire thread, What is the business model for Android apps?

Technorati Tags: davlik,   ubuntu,   android,   sdk,   logging,   webkit,   howto,   ubuntu,   eclipse, revenue, costs, profit