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

General Discussion

Ryan Harper
Ryan Harper
3,441 Points

Im interested in building my application but im having trouble getting started......

I've got an idea for a web application and Im having trouble with organizing my ideas. After I've written down wire frames of my application, should I jump into UI or work on the backend operations of the application(workflow and processes). If I begin in the backend, how do I organize my code...are these questions for a different forum, if so id be happy to hear from you. Thanks.

You said you've wire framed, so you have a basic idea of what your application is going to look like; in many web projects I've worked on its best to keep a basic UI until the backend is done. This is good for 2 main reasons:

  1. Depending on challenges and changes during backend development the look and feel of your app may change.
  2. While building the backend you may find there are more logical ways to approach the problem that will involve front-end changes.

Typically there would be a back-end development team and a front-end development team so this wouldn't be an issue, but if you're going to be a one man show I would start with an ultrabasic front end and fully build out the backend.

2 Answers

Usually you create frames as how you want your app or website to flow. Make them visual. Like mockups. Some people use Balsamic Mockups, or Adobe InDesign, or CorelDraw Graphics, or just simply paper and pen. You need to know where you are going first before heading that way.

Ryan Harper
Ryan Harper
3,441 Points

Ok, so making certain the user experience and interface are step 1. I will check out the tools you mentioned. I've never built a software development life cycle but im thinking this should definitely be a major component.

Thank you

Kevin Korte
Kevin Korte
28,148 Points

I would focus first on user experience. This will help you figure out what you need your back end to do. After the back end is done, than I'd last work on the user interface. Much of what Ryan Harper said is true. You'll likely find your user interface on the front end change once the backend is complete. I'd also keep the UI very simple until the end and you have a fully functioning website.

You may also have to adapt your UI to create a better UX.