Welcome to the most comprehensive course I’ve ever made! In this adventure we go through the following stages:

1. “I have no idea what to make”
2. Selecting our app niche
3. Researching the competition and revenue models
4. Planning our app
5. Coding the app (all mistakes included)
6. Releasing the app
7. Reviewing revenue and download numbers

There are absolutely ZERO EDITS. Everything is shown in real time, including decision making and research. You’ll even catch me copying and modifying code from Stack Overflow (because we all do it).

Over 22 hours of raw content will turn you into a grizzled veteran of software production!

Why no editing?

If you’re just getting into coding then you don’t really have a true experience of what day to day life is like. This course shows you that reality.

That’s why I left out absolutely nothing – even mistakes and buggy code. That way you get a real life overview of being a developer. about 70% of our time is spent correcting our own silly mistakes!

Why did you make this course?

I have over 800,000 students on many platforms and they all struggle with bugs in their code. This course is the antidote to their problem, primarily aimed at making an app production ready. As far as I know, no other course actually runs through this process.

If you want to experience the real life of a developer then this is the only course out there that will give you that!

Is this for Beginners?

You need to have some experience with code before you attempt this course. As a rough example you should know what classes / objects / interfaces are. In this course I explain some things I’m doing but not all of them (else we’d be here for months!).

If you want something extremely beginner friendly then have a look at Universal Software Engineering for Total Beginners.

What do we Make?

We will make an Audio Recorder app. It sounds simple – record and play back the audio. However, as a software engineer, “simple” often translates to “pretty complex behind the scenes”.

For example:

1. How do we design the user interface?
2. Does the design interfere with how we code? (hint: it does)
3. What are the software engineering practices required to make our code readable?
4. How few features should we include?
5. How much code is enough? Should we refactor often?
6. How to not get caught in endless feature additions and end up never releasing….
7. And so much more!