For access to native APIs unsupported by the browser or deployment to the App Store, you will still require one of the wrappers above.
But if you just want the general look and feel or a quick way to test how your game would look natively without going through the entire build process then there is another way.
In this article we will look at using
meta tags like
viewport, and others as well as a
manifest.json to give your mobile web game a native-like experience.
Add to Home Screen
Add to Home Screen has been a feature of iOS since the very first iPhone where you can save a webpage to the home screen and it will appear with an icon like any other app.
It can then be launched in full-screen mode without the Safari UI.
Setting this up couldn't be easier. You only need to add a
meta tag to your
<meta name="apple-mobile-web-app-capable" content="yes"> <meta name="apple-mobile-web-app-title" content="My App">
Android has a similar feature with a similar
<meta name="mobile-web-app-capable" content="yes">
The only difference is the lack of
apple- in the name attribute. While you can do it this way for Android, it is recommended to use the Web App Manifest instead.
manifest.json for games would look something like this.
Then add a
link tag in your HTML.
<link rel="manifest" href="manifest.json">
Status Bar Options
Games generally hide the status bar completely for an immersive experience. We can't do the same thing with this setup. You'll need a native wrapper.
But you can make it minimally intrusive by using this
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent">
This will make the text white and allow the web page's background color to show through. Better than nothing!
There's a lesser-known
viewport setting to go along with this for an even better experience. Check the Viewport section below.
By default, iOS will use a screenshot of the app from the last time it was launched as the launch image.
You can specify a different image with this
<link rel="apple-touch-startup-image" href="launch.png">
Android will automatically create a launch image from the
icons fields in your
manifest.json. You can't customize it but it is a lot less work. 🤷♂️
iOS will auto-generate an icon based on what was on the screen when the app was added to the home screen but you can specify a different icon with
<link rel="apple-touch-icon" href="custom_icon.png"> <!-- you can also specify specific images for different resolutions --> <link rel="apple-touch-icon" sizes="152x152" href="touch-icon-ipad.png"> <link rel="apple-touch-icon" sizes="180x180" href="touch-icon-iphone-retina.png"> <link rel="apple-touch-icon" sizes="167x167" href="touch-icon-ipad-retina.png">
meta tags are specified then iOS will look at the web root for these files:
For Android you need to specify the
icons field in your
meta tag is also the most important but you probably already have it.
index.html templates for mobile web apps include a
meta tag like this:
<meta name="viewport" content="width=device-width, initial-scale=1">
This will work well for most cases but we can do better than that for games.
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no, viewport-fit=cover">
The 2 key properties to look at are
Any zooming or scaling for a game should happen in the HTML
canvas element that your game runs in and not the webpage around it. Odds are your
canvas will already take up the entire page and this won't be a problem.
viewport-fit. It is lesser-known but it lets your game use the full edge to edge display on iPhone X and newer. You'll still have the status bar but at least your game will be under it. 😅
With these native-like features in place, you can prompt players to add the game to their home screen for the best experience. 🎉
You can also use it as a close approximation of a native wrapped game during development.
Combine this and the ability to test on mobile from your development server to vastly speed up your workflow.
Let us know in the comments below if anything doesn’t work or is unclear. We’ll be happy to fix or clarify!
Be sure to sign up for our newsletter so you don't miss any future Phaser 3 game development tips and techniques!
Drop your email into the box below.
Don't miss any Phaser 3 game development content
Subscribers get exclusive tips & techniques not found on the blog!
Join our newsletter. It's free. We don't spam. Spamming is for jerks.