Mobile App vs Mobile Friendly Website
When the idea of bust-it was presented initially the foremost idea was "it's a mobile game you can download from the AppStore". Well, why? To achieve a fully platform integrated experience in your application, then developing a native mobile app is probably necessary. But is it necessary to develop an application that can "help kids enjoy learning maths"? For our scenario the answer is probably no. But nor does this decision stop us from developing a fully fledge mobile app in a later phase. But how did we come to this conclusion? Well let's look at some of the reasons "mobile app" was being championed.
"It can be available offline"
Yes it can but it's not the only route to achieve this (PWA a discussion for another day). Mobile networks speed and coverage is "apparently" improving (have you tried it on southeastern trains? I take that back) so this is at least lowering the barrier to the online only approach.
By making an offline application you aren't removing the requirement that you need to be connected online to download the application in the first place. This likely will be a sizeable download and raise the barrier for it to be useable before it's install.
We also want bust-it to become a multi user shared experience, sharing challenge links with friends hopefully driving use etc and to do that you need (at least at that point) to be online.
The "AppStore"
It is an effective curated experience, to search and install an application. It also seamlessly integrates your app in to a user's mobile. There is no escaping that this it is a better user experience. Even though shortcuts can be added to the Home Screen and PWA can look like a native app. But what mobile apps vs websites do you use? Is the absence of a mobile app a barrier to using the service? At least in our experience no. In fact in the area of puzzle games when you think of the likes of Wordle or Nerdle you could reason you are first drawn to the websites before investigating whether there is even an app or not.
Advantages of this approach
"The clutter of downloaded apps"
How many apps have we downloaded to our mobiles to sit there doing nothing but take up storage space? This in its self has put me off just downloading yet another app, even for trialing it. Would this be a barrier from other potential users for trying the game? There is minimal download for the use of the website and updates.
"Cost"
Cost of the initial development for mobile devices can be more expensive than for desktop or a website. Factor in developer licences for Apple and Android, hardware to develop on (eg Mac for Apple, devices for testing). While we are not suggesting there aren't ways around some of the issues, you do need to factor in how difficult and how good an approximation alternative is or the extra time that is an overhead to the work around.
"Maintenance and Speed of delivery"
All applications should involve maintenance, bug fixes, dependency updates for known issues. Factor in two major operating systems and the supporting devices for mobile app development. There is no denying that you are multiplying your support requirements. The same advantage applies to the initial delivery of the application.
"Don't forget desktop"
Going by tracking numbers half the audience can be desktop for bust-it. Are you potentially blocking potential users that could be served by the same solution in a website that is mobile friendly.
"Limitations of mobile friendly website"
One of the limitations of mobile friendly websites is that they cannot fully utilize all of the native functions of a mobile operating system. Not an issue for our game but obviously something to consider for other applications.
Next to consider is browser security. With every iteration of browsers it seems there are more restrictions to favour privacy but that might restrict on what you can do with your website. While that's a good thing, it stopped ideas of sound effects on tiles dropping etc for our use.
Lastly, Mobile-friendly websites can’t run in the background, which could cause issues for apps like fitness trackers and messaging apps that require continuous operation but not for our maths game.
“In Closing”
There are for's and against points for any solution. You can reason either way (and I sure that there are people that would) but stopping and thinking even if a develop route isn't the coolest option, compromise may save significant effort and cost. The AppStore experience is definitely a draw for us. Again there are routes to take a mobile friendly website to something hosted in an AppStore that isn't starting from scratch.
At the moment though for our scenario a mobile friendly website gives us the benefits that fit our requirements.