10 Ways To Doom Your Next Mobile App - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Software // Productivity/Collaboration Apps
News
8/16/2016
07:06 AM

10 Ways To Doom Your Next Mobile App

There are many ways to mess up mobile app development. These 10 will get you to #fail the fastest.
2 of 11

Build In Too Many Features

We've all been in those developer meetings. You know, the ones where everyone looks at the application's purpose and starts throwing out features to make it better. Then comes the magic moment when you look at the list of possible features and decide each and every one deserves a place in the app. Hey, you're using an agile discipline so you'll sprint your way to the most full-featured app ever, right?

This decision is where the wheels start to come off your app development effort. There's nothing inherently wrong with an app that has all the features necessary for the work flow in question. But it's better to be ruthless sooner rather than later when it comes to focusing your effort and pruning extraneous features. If additional features become necessary later, then you can add them as part of the agile process, or even create another app focused on those features. Keep things focused and you'll greatly increase your chances of creating a winning app.

(Image: KEMAL BA/iStockphoto)

Build In Too Many Features

We've all been in those developer meetings. You know, the ones where everyone looks at the application's purpose and starts throwing out features to make it better. Then comes the magic moment when you look at the list of possible features and decide each and every one deserves a place in the app. Hey, you're using an agile discipline so you'll sprint your way to the most full-featured app ever, right?

This decision is where the wheels start to come off your app development effort. There's nothing inherently wrong with an app that has all the features necessary for the work flow in question. But it's better to be ruthless sooner rather than later when it comes to focusing your effort and pruning extraneous features. If additional features become necessary later, then you can add them as part of the agile process, or even create another app focused on those features. Keep things focused and you'll greatly increase your chances of creating a winning app.

(Image: KEMAL BA/iStockphoto)

2 of 11
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
DDURBIN1
50%
50%
DDURBIN1,
User Rank: Ninja
8/17/2016 | 12:03:47 PM
Time vs Cost vs Qualtiy
Pick any two and the third will suffer. In my experience management is in denial on this concept most of the time particularly when the "features" list runs the lenght of the building and down the street changing from week to week. Expectations are all can be delivered and done perfectly at a fixed time at a fixed cost no matter the number of features added after the project gets started.
News
Think Like a Chief Innovation Officer and Get Work Done
Joao-Pierre S. Ruth, Senior Writer,  10/13/2020
Slideshows
10 Trends Accelerating Edge Computing
Cynthia Harvey, Freelance Journalist, InformationWeek,  10/8/2020
News
Northwestern Mutual CIO: Riding Out the Pandemic
Jessica Davis, Senior Editor, Enterprise Apps,  10/7/2020
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
[Special Report] Edge Computing: An IT Platform for the New Enterprise
Edge computing is poised to make a major splash within the next generation of corporate IT architectures. Here's what you need to know!
Slideshows
Flash Poll