Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Android

How do you normally start creating your android app?

Hi,

I just would like to know how to normally create your app. Do you normally start everything from scratch or do you also rely on sample code or source codes than can be built on?

Thanks in advance!

2 Answers

  1. Idea
  2. Define functionality (pen and paper)
  3. Define classes based on 2 (pen and paper)
  4. Then basically like the treehouse course does

Thanks Geert. Also, do you rely on sample codes somewhere or just the android developer site?

Start from scratch. Build you're code from a psuedo code plan.

Oh Ok. Thanks Marcus.do you also rely on sample codes somewhere or just the android developer site?

Ben Jakuben
Ben Jakuben
Treehouse Teacher

This is pretty much how I go about it. Program design can pay off, but I like to dive in and do stuff and refactor as needed. I tackle one problem at a time and pull in sample code if I need to. I do keep track of things to do in the app by documenting them in the code itself. I like to pick a central spot and make a TO DO list in comments, like putting them in the main Activity or an Application subclass, if one is present.

Great. I see that's the way a professional would approach their app creation. Thanks so much for sharing Ben!

Ben Jakuben
Ben Jakuben
Treehouse Teacher

You have all the control when working by yourself, but if working with a team, you'll need to find the best approach that meets everyone's needs. In that case some thought behind design as a group can really pay off, or at least constant communication when working on components that affect other people. Happy coding!