Separating must-haves from nice-to-haves

The best way to ensure that apps are actually finished and deployed, especially for smaller teams or one-person teams, is to ensure that the app will not be too big. A good rule to remember is--ship early, ship often. These days, with app stores for all sorts of platforms and devices, including the HoloLens, updating an app is easy. Most of the time, the user does not need to do anything. He will just be aware of a new functionality in his app all of a sudden. So, ensure that your app is in the store as fast as you can, and then start updating it.

To get the app in the store as quickly as possible, you have to trim your list down to the bare essentials. This is my attempt:

• Note incoming plane type
• Note incoming airline
• Note outgoing plane type
• Note outgoing airline
• Take pictures of the planes
• Look up date of first appearance of a plane type
• Note the runway planes use

I have removed the pictures function and the looking-up functionality. I believe that they can be strong features that really make my app shine, but I do not necessarily need them in the first version. Apart from this, I am not entirely sure how to take pictures from the device, so I want to investigate that later on, when I have a little more time. This way, I am removing all risks that might delay shipping version 1.