User journey

So many times I have seen the user journey neglected by budding app developers. Again, I’ll hold my hands up and say that sometimes I’m so excited by the prospect of what my app could be, that I just dive straight in and start creating. This has then meant that I’ve ended up missing key considerations with what my user journey through the app is going to be.

What I’ve found more useful though, is by planning the user journey before I start writing. So what does this mean to you as a developer? It means that you need to firstly consider what does the user need to do in order to achieve an affect e.g. my user needs to use the app to create a new entry in a system, and my user needs to use the app to update an existing entry.

Once you have your key activities noted, you can then start to plan how the users achieve that. For example, if my user wants to create a new entry, they have to click a button to open a new form, which they then fill out and...