The first problem to be faced by all those who have decided to develop an APP for Android, is how to give it visibility within a catalog application that counts now more than 200,000 APP. It's not just about developing a technically perfect APP but beginning to understand the behaviour of consumers and especially what can make their eyes a APP interesting, entertaining, useful, captivating etc. Counts a lot the name under which it distributes the APP, its icon, its description on the store. Also after the eventaule download is important that the application is used and raccomnadata to others.
The best applications usually share some basic characteristics and should
to be portable and secure the same functionality on later versions of Androidessere updated frequently and regularly with the addition of new funzionalitàfunzionare properly (no ' bugs ' and rapid intervention for their solution in case there were any) be consistent with the conventions of standard Android interface for performing graficaessere and do not consume excessive bandwidth, memory and batteriaessere perceived as new and creative (surprise) should be used ferquentementeutilizzare graphic content, audio, video, etc. qualitàessere's intuitive and easy to use (no manuals or guides should serve to use) be accessible to people with disabilitàdare good reasons a user to tell his experience with the application to friends and colleagues to suggest downloading and usofornire additional content if the applications are data-think drivenessere and built to a mass distributionAs listed above is described in more detail in the section Best Pracices help for developers Android (Android Dev Guide) which afrontato the topic of application compatibility, portability, multi-screen support, user interface, performance etc. :
Compatibility: essential before determining on which devices and which version of the operating system the application should work. The APP must be supplied by ' use ' features (audio, bluetooth, camera, camera auto-focus camera flsh, location, etc.) so as to allow the Android Market to filter and categorize your APP appropriately. You can define filters for downlod in locations and different Nations.Supporting Multiple Screens: The Andorid SDK 1.6 and later versions support different sizes (misra diagonal) screen and different values of pixel density (distribution of pixels on the screen). Android provides four types of screen (small, normal, large and extract-large) and density (low, medium, high. extremely high). Touches to the developer to define the size and the reference value and possibly prevedre the possibility to adapt the application to different screens and devices so it's Android to optimize everything depending on the device used by the user.Supporting Tablets and Handsets UI Guidelines: fundamental follow the guidelines provided in the Guide for Android sviluppaori. The guide provides useful indications for the design of icons to be included in the APP (menu, status bar, tab, dialog boc etc.), widget (app protector pro android widget agenda, battery life, stock alert etc.), and menus.Designing for Performance: an APP must be efficient and take into account that the device's resources are not infinite. An APP must not occupy device resources for a long time and remove the cache file to close the application.Designing for Responsiveness: the code must ensure speed and efficiency in load application and the processes associated with it.Designing for Seamlessness: application configurations must be appropriately managed, ensuring safety and security of user data.Designing for Security
Registration and publication of the application requires the developer to register through the creation of a special account at the Android Market.
When registering you pay an entrance fee. Android, unlike other store applications not bound to follow a formal process of approval but simply requires the subscription policy for all developers. If your application violates in any way the policy can be removed at any time by Google.
To commercialize an APP must have an Account (Google Checkout merchant account), available to all developers in 29 countries around the world. After registration and login through the login procedure for configuring the account using the link to Setup:
provide private information to Google to communicate the developer/accountfornire customer support information so that users of your application know where to turn in the case of necessitàfornire bank details for payment of debts accrued through the sale and download of applicazionisottoscrivere the conditions of service offered by Google that describe payment terms, types of transactions allowedprohibited actions, deductions due to Google (30%) etc.Precise and formal procedures for the management of the account serve to ensure the developer from fraudulent use of his identity and UserID.
Payment through Google Checkout more or less the same way offered by PayPal, a service that could be made available in future as an alternative to Checkout.
To prepare properly to the publication of a guide APP for Android Developer suggests a series of verifications (checklist) and some testing.
The checklist includes:
verification of the functioning of the APP on Android devices diversiAssegnare to version APPAttivare and disable the debugging and the loggingOttenere/create an encrypted key to use when accessing the applicazioneCompilare applicazioneVerificare which features the login procedureAfter the necessary checks you pass to the phases of tests to make sure that all of the functionality provided by the application to function properly on different devices. The emulator can be a solution but it is suggested the test directly on the target device because the emulator is lacking or is missing the following functionality:
USBBluetoothSensori connections (accelerometer, proximity sensor, barometer, compass etc.)Determination of batteriaDeterminazione charge of insertion/issuing a device esternoFoto-room and videoHeadphone... more
