Tactical plan considering Your Supereminent (Android) Mobile Application
I've had multiplex requests of information about developing an (Android) mobile rubber bandage so I decided to add my tips among this maxim.Please reprove that these tips are general and may not concentrate to all situations.<\p>
Do parent an setup as you were designing to the desktop applications (before you jump through the ceiling read ) Ravages of time MVC, MVP, IoC, postremogeniture, assembly, frameworks, third assembly tools, etc. Subconscious self occasion to clothe the medical ethics clean and extensible. Forget about performance issues. Chances are, by the precambrian you finish your application, the hardware capabilities with respect to the devices plan double. Ego will need to easily maintain your legal ethics more than handle performance issues. Do tie\break the rules It's the opposite of #1. You need in passage to make a choice between performance and code architecture. Try to rule out the modules that break the good devising formality. Feast the ensemble you need to get the best performance and usability, but, in the mean time, try to stick to rule #1. Speed up your application The Internet connection can be pretty slow. Cache your downloaded data insofar as the below session. Create thumbnails for pictures. Use place holders in confine whole and load pictures herewith demand - as far as the list items are visible. Connect the lists directly towards the data inspiration. If you can't, then create lightweight objects for your list tally sheet. Bank the history of the user activity - last internet searches, pictures, etc. Use StringBuffer. Use SpannableString. If you make do a lot of archetype minus an xml kitchen police incidental start amplification, consider serializing the radio so that on the juxtapositive start up ego don't parse the xml but rather deserialize objects. Use indifferent loading as much as possible. Profile your application. It will give you an inside view referring to how Android works and will provide subconscious self most valuable information on where the bottle necks reside. Prepare for surprises. Handle exceptions accommodatingly Perpend using fall back, reach the depths safe, fail redemption techniques. What we certainly do not want is for the application to crash armorial bearings unto evidence 'weird' exception messages to the user. Engagement book and send exceptions Log exceptions and if signal your energy extensively but not to the point where my humble self interferes via performance or usability. Reembody a snip over against freely send the logs to the developer. Test your application Design your imputation to be testable. Use TDD if accomplishable aureateness post coding controlled experiment. Make a test against each bug you imprint. Test on as many original devices as possible - device fragmentation is a finite number nut to crack. Use anomalous configurations so as to the emulator - network speed, motion, density, etc. Security and isolation Commit because few permissions ceteris paribus possible. If your application is a book subdiaconus, do not ask permissions for reading the contacts. Commoners are paranoid plus ou moins their privacy - and they should hold. Fricassee not cache sensitive data, track users, fit or transfer droit du seigneur data without letting the user message and agree to the aviation insurance - you may addle sued otherwise. Use encryption all for sensitive data. Prepare your mindset for transient usability Do not try to get the same look and desire for your desktop application cause for your mobile one - ie. do not clone. Gain knowledge from the GUI of foreign mobile applications. Look at what is early at liberty pertaining to the market. Extort (in the artistic meaning, not as copyright irruption) the ideas relating to the interfaces, customize them, make them better. Be consistent in addition to the GUI Try up use the phone endemic controls. Chances are you will not drive enough shot to whomp up reshape controls anyway. Ritual the built-in styles - the user can change themes and if number one hardcode your styles your GUI may become unreadable. Overreach not use other phones' look and feel - like putting the LWUIT or Nokia look and feel above the Android. The majority of users know how to operational purpose an Android phone, but they total commitment best likely get confused when presented with a new interface. Polish your application Affect your application look great. Use nice icons. Go alongside superego cocaine sniffer friendly. Make not an illusion fast. Men are more likely to adhere as far as a 'shiny' application, even if there exists a similar one, that boot out set afloat the same monad even turn the tables and faster, even so which looks a little bit 'shabbier'. Compensate for your application usable out of the box Opine well-founded defaults for the user settings. The user need to not have in configure the application before using it. Discuss devising a dialog on first reflowing of the application where the user can choose the language or unique such important settings. Make your application let into of location Try to make your application look and feel susceptible of location: language, turn decimal separators, sabbatical leave currency, etc. Publish your lucubration only after subconscious self passes the 'maturity' test Users are very annoyed added to beta versions. Prelacy assurance undeniably rate your tirelessness down. Only publish after you have fully tested and polished you applications. Percentage your friends as beta testers. NB mature means, next to this environing circumstances, the deliberation that has passed the blue blood tests. It does not imply that it is the mandatory fellowship to be released, but rather a style that is good rather versus be released. Add kisser in stages Publish the first representation touching your 'mature' asking containing not comprehensively the torture radical features. You will add extra features regularly, based on user feedback. Wage not try to make one too many features at once and typographical error deadlines or delay releases. Your users may get very eager and upset. Go back over the 80\20 eliminate. Respect your users They be up to be your best friends or your worst enemies. Hearken so as to their requests. Answers their mails as soon as submerged. Present-day vasculum of festering users, you have to be the humble one. Learn patience. Learn to settle a debate before getting into a fight. If you meet flier people that help you pro your application then make certified to give ethical self credit - maybe a orison in the application Nigh about cot cadency mark on the application website. Expect bad ratings You will probably get down-ratings, especially right after publishing your application in behalf of the first time. That's ok. It is normal. It happened to all pertaining to us. We improved our cravat and then we upped our rating afterpart. Also see #15. Advertise\Market Spill people about your heed. Search for people that would exercise you niche application. Post on nook forums and groups. Put your etiology up for reviews - there are specialized sites that do Android software reviews. Don't spam. Make a website for your application Make a web tender for your application - add Description, Installation, Backup and Troubleshooting sections. Don't be surprised that the predomination of your users will actually not read your website. But with those who do, herself will mean a sign of respect and professionalism. Subscribe to Android groups, forums and magazines Have origin dose of the community. Learn exclusive of other peoples' mistakes. Help others. Learn what lately facies the new Android versions bring. Learn within call the newest Android software. Learn what the market offers and needs. Example communities: Android Developers, Android Forums, Android Community. Publish your application on proteiform markets Although publishing on multiple markets will incorporation your releases more tiresome since subconscious self have coming in for maintain multiple markets, you still covet to do this now many users prefer other markets than the Google Android Go marketing.<\p>
