Peter Bravo

Dev Marketing - Dev Marketing
London - United Kingdom

    3 Tips For Avoiding the Common Missteps of App Development

    April 19, 2017

    Developing an app is something that many businesses and companies have been getting into, with the growth and development of the mobile industry becoming an enormous drawcard for business owners worldwide. As far as user engagement tools go, the mobile app is right up there in terms of getting users to actively work with a business or brand. So it stands to reason why so many companies would be using apps as a means to reach more users.

    And we would be excused from thinking that it was super easy to make an app - all you have to do is map out some wireframes, set out your direction and you’ll be rolling in customers and engagement. We wish this were true but the fact is that making an app is harder than you think, and there are some common mistakes that pretty much everyone who is new to the game makes.

    Because these mistakes are so common, they’re also easy to avoid and, because we’re nice like that, we want to share some of our top tips for avoiding common app mistakes! After all, there are plenty of misconceptions about developing app, and the sad fact is that many mobile development noobs end up making mistakes and wasting time and money on learning that they simply don’t have.

    Build native every day of the week

    It might seem, on initial appearance, that building an app which works across multi-platform situations makes sense. After all, your developers only have to code something once and then you can push it out across every device. But - as Facebook’s Zuckerberg pointed out after Facebook started to grow and turn into something huge, the original reliance on HTML-5 was one of its biggest mistakes.

    While it might be the easy route to create an app that fits across a range of platforms, it makes it far harder for you in the long run. A cross platform approach will still lure startups that don’t have the resources or time to invest in developing separately for each operating system (OS) - but we warned, if you don’t, you’ll end up spending more money.

    Confirm that your backend is ready to support mobile apps

    While you might be raring to go, the fact is that your backend might not be totally ready to support mobile apps. You may very well need to change or upgrade things to create the best possible mobile experience. If you don’t have the right kind of API design and the right kind of implementation you will get an app that may look great but perform poorly in the real world.

    Take a bank as an example.

    Where once people might have checked their bank balance once a week online through a web browser, they’re now checking their balances upwards of 50 times a day. Can your back end handle that kind of traffic and workload? You need to check:

    Maximum payload size
    Low latency
    Single API call per screen
    API version number in parameters

    Building your app yourself will take you many, many times as fast as an expert outside firm

    Don’t make the critical error of thinking that just because you have HTML, CSS and Java abilities within your team that creating a mobile app is going to be easy. Unless you have a dedicated mobile team, you’ll find that your internal app is going to eat up your time and get pushed back because it’s being paid with in time, instead of money.

    If you’re thinking about building an app as a business, you need to consider that there are a great many companies out there whose main job it is to create apps and to deliver an end product that is exceptional, every time. If you’re thinking of creating an app then make sure you avoid these common pitfalls, and if all else fails get the experts on board.

    Read Peter's other blog entries >

Please Wait