Planning your core feature set
The first step when building an app is to plan your core feature set. The guys at Fueled, a design agency in New York call the feature set your project’s bible, and it’s a great way of looking at it. In the same way a house needs blueprints, an app needs a feature set.
While our perception of the user interface might be that it is often a moving target, where changes to the elements on the page are made quite frequently, what often happens is that the general structure and layout as defined in the wireframes, if well-designed, stand the test of time.
If you think about Facebook, Google, Skype and other websites we love to use every day… the basic layouts don’t change very much after the first year or two of launch.
Facebook in 2006 (founded 2004)
Google in 1999 (founded 1998)
If you are more than two years into your app, and you are looking for product/market fit, of course the user interface and user experience plays a vital role in that so it makes sense to make the necessary adjustments.
By the way, two years or twenty years, once you are doing what you love, and you want to grow your business, you’ll make it awesome and the right business for you! Rome wasn’t built in a day, and Coca-cola sold an average of nine-glasses per day in its’ first year of business. Every business was a start-up at some stage.