How long does it take to design an app?


#1

I know this is a bit of an ambiguous question, however, I arrived at work this morning to be told we are expected to turn our very complex web app into a native mobile app, for both ios and android, and have it released by the end of the year. We are getting a contractor to work with myself for the UX and UI design, and also a contract developer, however I am wondering if this is an unrealistic business expectation?

I have never designed a mobile app before so have no idea of the process a mobile app expert will go through and their time frames. Can anyone provide any estimates for me please?

Thanks in advance!


#2

As you say, this is something of an ambiguous question. I believe in all honesty, though, that even if we knew everything there was to know about your app, the best answer we can give is “maybe.”

The process a mobile app designer or developer goes through is generally very similar to the process desktop and web app designers go through. The biggest difference is the constraints that they face, which can cause particular problems when considering developing for compatibility between many different devices and screen sizes. Usually one of the first things decided is what range of devices will be supported, allowing the design and dev team to get a foothold to begin the rest of the rest of the climb towards a finished process.

The next steps will be to define what milestones you’ll need to work towards, and what you’ll need to design and develop and reach those. This is important as the very nature of our business is that nothing is ever truly done, but merely exists in a supremely usable state at any particular moment. In an Agile environment, having established those goals, your team will develop features, user stories, and tasks over the course of the Agile planning process to help you get there.

If you have good developers and designers who are familiar with the constraints of these cross-device compatibility issues, then the process from this point isn’t much different from normal. You’ll follow your teams development organization method (likely some variety of Agile) with a goal of having passed certain milestones by 12/31.

As you can see, a lot of the team’s success or failure is going to depend not on your ability as a UI/UX professional, but on the efficiency of the planning, development and QA processes going on elsewhere in your group. Even the best designers in the world face dependencies that they can’t control. What we as design professionals can control is how we manage and execute our deliverables, hopefully in a way that makes it easy for others in the process to keep the ball rolling.


#3

Thanks for your help. I thought it was going to be a difficult question to answer, but you’ve certainly made some things clearer for me :slight_smile:


#4

No worries, I’m happy I can help out!


#5

@dougcollins, I would add that focusing on iterative releases might be a key factor to managing client/boss expectations. The proposed products should probably be broken down to identify what is the Minimal Viable Product (MVP). What is the smallest piece of functionality you would care to deliver and when can you deliver that piece?

@jacquidow, Think about the final application being a sum of its parts. What do you need at a minimum to go live in one year and what functionality is nice to have but possibly not essential to creating a product that might be considered, “successful”.

In my job I’ve learned never to say, “I don’t have time for all of this” instead I say, “here’s what I have to do, what do you (boss/customer) want me to focus on first?” Then, with that priority in your pocket you can start to set expectations on what other tasks may or may not be completed on time.

Sounds like a tough situation. I wish you the best of luck.


#6

Thanks for this. Luckily I have 2 really good BA’s working on the MVP and prioritising with stakeholders. Just need to keep everything crossed it all goes smoothly.