For however much you may know about a particular subject, there’s likely to always be more. What you don’t know, can help you. When setting out to create a mobile app, utility or game, you likely have a vision of how the completed app will work, how it will look, and all of the things it can do. It is worth taking some time to go even deeper.
One of my recent projects involved creating a scenario for The Falkland Islands War between England and Argentina in 1982. That’s a very small project in comparison to my World War II “War in Europe” projects. The Falkland Islands was a small war, lasting only about two months with each country fielding only about 2 brigades each. Yet, for its small size, it includes all of the complexity of much larger conflicts.
In games like this, typically only a few things are really needed – the map, the units involved (Order of Battle), the equipment in the units (Tables of Organization and Equipment), when using a game platform like The Operational Art of War. With this collection of information, one can roughly recreate any type of battle from Alexander the Great to Napoleon to modern warfare engagements.
But a wide range of other factors can be taken into account. Nevertheless, even considering all of the things that you can apply to a game’s design or an app’s functionality, there are a lot of things that are easily overlooked. It is safest to presume from the outset that will be the case.
Asking for help is not a sign of weakness. Turning to other professionals to get their insight can transform an average app or game into an excellent one simply by listening to what they have to say. This can work for any number of social and professional networking platforms such as LinkedIn, Quora, MosaicHub, and others. Most especially, sign up to groups relevant to what you are working on. Explain what you are aiming to do and ask if anyone has anything they would like to see included.
The devil is always in the details and it can be that extra little complexity that makes your app unique enough to stand out against so many other apps, utilities and games. You might be making a utility app for medical students, but getting the input of doctors, nurses, insurance processors, possibly pharmacists, can broaden your potential list of functions. Ultimately, you decide which functions you will include but without reviewing the input from each user segment can mean not implementing some really easy things that will help your app shine.
Enough people are happy to lend their expertise to more than justify the effort. The level of professional input I received on this particular game project exceeded my expectations several times over. Most of it was easily implemented and essentially “makes the game complete”.