Make an app in 12 steps
Image from MockPlus.com

Make an app in 12 steps

The title makes it sound WAY easier than it actually is.

By Philip Simmons

1.    Define a Goal.

I know it may seem out of order to have a goal before having an idea. However, having your goal clearly defined FIRST will help with outlining your idea more effectively. Having an idea is good, we all have great ideas but, in the words of Albert Einstein: “If you can’t explain it (your idea) to a six year old, you don’t understand it yourself .” And, if you don’t understand your idea… How will anybody else?

2.    Research.

Try to find as many apps as you can that have the same goal as yours. THEN, find things that you think are missing or easier way to do something that may take less clicks or scrolling for example.Basically your finding the“thing” that will make users choose your app over another. In laments why would they choose your app if there’s already one that does everything they need already.

3.    Have an idea.

Come up with something, nearly anything really. BUT, try to make it something you or hopefully someone else (many someone else’s) will want to use continuously. Remember every idea doesn’t have to be grand to be successful. Fidget spinner anyone?

4.    Outline it.

Sketch out your app. Listen, I know what you’re thinking. “This is tedious and I know what I want it to look like already.” Trust me. What you have in your head and what comes out in code ARE NOT the same. Having your app sketched out or outlined visually previous to typing your FIRST line of code helps you determine so much. Such as, what stack to use, what CSS library to choose, how to market your project after its done, etc.

5.    Mock it up.

Take your sketch and translate it into its basic components on the web. This simply means build out all your pages. No API calls, no databases, nothing complicated. There are many free online tools to do this with. A few popular ones are Lucidchart, InVision and Moqups.

6.    Choose a Database.

Choosing a database is super important…. SUPER. This step decides how quickly your app will run if (WHEN… positive thinking) it becomes popular. Or, how it will perform when it has to be scaled at different stages. Research relational databases (i.e. SQL) vs. non-relational databases (i.e. MongoDB). Then, research how making queries will effect your app under different conditions.

7.    Start Coding.

Here’s where we get to the good stuff for developers. If you have made it to this step you’re half way there….. conceptually. “And, the conception phase is half the battle.” By now you you’ve chosen your stack. Here is where you define your models, back end language (i.e. C#, Node, Java etc.). Build out your API, get your front end talking to your back end. Make your calls are working.

8.    Have it tested.

This step is a little scary because this step is where you ask for help. Yes, help. Call a friend, call a few, preferable other developers and ask them to test every route and add info to your DB and give you feedback and bugs (there WILL be bugs).

9. Debug it.

This step is simple in phrase. We all know debugging isn’t easy but it’s essential to making sure your user has a good experience.

10. Make it pretty.

Until this step there has been no mention of margins and padding or transitions. Until this step there has been no need to make your app look nice. Up until now getting it working is the only thing that matters. Here is where you look your artist flow. Using your wire framing and sketches of course.

11.  Have it tested… again.

Tested? Again? Yes, tested again. This time by a non-developer. You want a typical non-technical user to test your app. They’ll find ways to break it you and another developer wouldn’t even consider!

12.  Deploy it.

You’ve spent countless hours, sweat, maybe tears on your idea. Let the world see it!! Good luck!

Great simplification of the app development process.  This is a good explanation for not so technical people!

This is awesome. Tough to see that the fun doesn't begin until step 7, but it definitely makes sense. I could probably have saved myself a lot of time on a few projects if I'd followed these steps before just diving in.

To view or add a comment, sign in

Others also viewed

Explore content categories