Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7692937
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T20:58:03+00:00 2026-05-31T20:58:03+00:00

Can anyone point to a good source or come up with a brief listing

  • 0

Can anyone point to a good source or come up with a brief listing of conceptual android programming DONT’s when designing an App?

I dont want my question to be vague, so I’ll give dummy examples(which might not make any sense or may be completely incorrect) to explain what kind of answers I am looking for are things like :

Eg: Avoiding these help you design/program robust android apps

  1. Dont acquire wake locks when waiting for a server response OR Dont have this logic in OnReceive of a broadcast listener…
  2. Extending IntentService is better than extending Services in blah blah scenario
  3. Dont create threads inside OnDestroy() for activities…
    etc
    etc

I hope you got the point. I know these could be infinite do’s and donts but I am looking for the most important basic ones that a beginner/novice should keep in mind so that they good be better android programmers.

Thanks!

EDIT

By Design I mean both the programming(logic) as well as the UI and not the look and feel alone.

Infact more importantly the ones that comes with experience and are not mentioned in books or tutorials because of the nature of these principles/tricks. They might not be absolutely right or wrong but are better or worse. Because they will not teach you a new concept but will help you get rid of a bad programming/design habit.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T20:58:05+00:00Added an answer on May 31, 2026 at 8:58 pm
    1. The very first most important aspect of mobile app development is the look and feel of you app. Here are Android design principles which give you killer design skills.

    2. This is an excellent resource I’ve found, it is written and explained by Roto Meier.

    3. What would be a better teaching guide than Android Developers site itself

    4. This is a single resource which is very helpful if you are starting out

    5. Here is a same question which was asked on Stack Overflow

    6. Android 4.0 enforces strict mode so check this out to know what that is

    7. To design a perfect app on any platform the first basic thing you need to know is as of how to divide operations into tasks so that the app runs smoothly, multithreading is an important aspect of Mobile development, this is an excellent link that shows you how to make Multi-threaded Android apps

    8. Ofcourse there is also a need to test you app on different devices just to make sure the UI looks perfect, and the app runs smooth. You should also make sure that your app runs on screens of different sizes.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Can anyone point me to a good source of example SVG code? Google charts
I need a CircularBuffer IDictionary. Can anyone point me to a good open source
Can anyone point to a good unified comparison of various AJAX libraries? I've read
Can anyone point me to a good resource (or throw me a clue) to
Can anyone point me to a good introduction to coding against the paypal API?
Can anyone point me to a good, simple, example of a Google API (AJAX
Can anyone point me towards some good documentation / code examples on how best
Can anyone point me to a good example on how to implement nested vertical
can anyone point me in the direction of a good tutorial on how makefiles
Please can anyone one point me to a good tutorial that helps me to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.