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 trialRandell Pur
4,934 PointsI know this might seem weird but I don't know how to start building an app.
I went through the iOS course, I was able to follow everything and understood it so that's not the problem. It's when I open Xcode I don't know how to start or what I should do. I have never built an app outside of the courses on here and it was easy to follow along and some of the apps already had some of the code written so it was easier.
Could someone point me in the right direction on what I should do?
I know this might seem weird but I am stuck and I freeze up as if I never used Xcode or written swift before, even though I have been every day for the past few months.
1 Answer
Cooper Runstein
11,850 PointsA good idea is to start away from the code, take out a pen and paper, or a note taking app, or use https://trello.com/, and write down what your idea is. Then come up with the really high level concepts of the app are, say you're making a weather app, you might need to get the users location, get the info, and display the results to the user. Then dig deeper into those, what is required to get the users location? Where are you going to get the info from? Record these steps as well. Then, start breaking down these into smaller tasks, and begin to think about the order of implementation -- you can't get weather data until you have a location, so this obviously comes first. Also note that you shouldn't be worrying about HOW as much as WHAT. You'll then have two important things, 1. a list of bite size issues/features you can tackle, and 2. a general idea of the order you need to tackle. Now that you've got that setup, whenever you face that programmers block, for lack of a better term, go to that list, and pull off a task, and begin writing the code for it. Realize that this is a living, breathing process, your specifications will probably change, you'll probably rethink a lot of the details, but by having a roadmap, you'll be able to always have a path forward.
Randell Pur
4,934 PointsRandell Pur
4,934 PointsThank you! Putting it that way and following those steps would make it easier to have the ideas and seeing it on paper will provide a better understanding of what I need. Thank you for the great advice.