How do you build an app? Part 2 (Code)

Sarah Smith
11 min readMar 8, 2021
Four people stand in front of the Apple Store in Brisbane’s Queen St, one holds up a cellphone which displays an image of the four.
Queensland app developers, show how to code an app James Bowling, Sarah Smith, Cameron Owen and John Passfield. Picture: Annette Dew Courier Mail Oct 2014.

What is involved in building an app? Who do you need to talk to you when you’re building it? Can I build my own app? Can I outsource building my app to developers overseas? Do I need to know how to code an app?

You’re reading the second part of my two-part post on “How to Build an App”. If you haven’t read part 1, start there to get the background for what I’ll cover in this post. I’ll be launching straight into discussion of how app building teams work, and that foundation will be critical to understanding this post.

This post 1 & 2 builds on my previous one What kind of apps are there?. If you haven’t read that now is a good time to check back there, just in case some of the concepts from there that I refer to in this post don’t make sense.

With this two-parter, I’ve got halfway through my series for folks who looking for how to code or build an app. I talk about the series in a special introduction post, which is definitely good for perspective. Check that introduction for context to the whole series, and links to the other articles.

Don’t Bury the Lead

In part 1 I looked at the critical process & team setup for app building success. The last specialist I will look in that team is the engineering manager. Also this person could be the team lead, project manager

--

--