Skip to content

Commit e8c441e

Browse files
authored
Merge pull request #5843 from Calinou/exporting-html5-mobile
Add optimization tips for mobile in Exporting to HTML5
2 parents 9c55731 + c1c1bbe commit e8c441e

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

tutorials/export/exporting_for_web.rst

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,27 @@ versions supporting WebGL 2.0. Note that Safari has several issues with WebGL
8484
2.0 support that other browsers don't have, so we recommend using a
8585
Chromium-based browser or Firefox if possible.
8686

87+
Mobile considerations
88+
---------------------
89+
90+
The Web export can run on mobile platforms with some caveats. While native
91+
:ref:`Android <doc_exporting_for_android>` and :ref:`iOS <doc_exporting_for_ios>`
92+
exports will always perform better by a significant margin, the Web export
93+
allows people to run your project without going through app stores.
94+
95+
Remember that CPU and GPU performance is at a premium when running on mobile devices.
96+
This is even more the case when running a project exported to Web (as it's
97+
WebAssembly instead of native code). See :ref:`doc_performance` section of the
98+
documentation for advice on optimizing your project. If your project runs on
99+
platforms other than Web, you can use :ref:`doc_feature_tags` to apply
100+
low-end-oriented settings when running the project exported to Web.
101+
102+
To speed up loading times on mobile devices, you should also
103+
:ref:`compile an optimized export template <doc_optimizing_for_size>`
104+
with unused features disabled. Depending on the features used by your project,
105+
this can reduce the size of the WebAssembly payload significantly,
106+
making it faster to download and initialize (even when cached).
107+
87108
.. _doc_exporting_for_web_audio_playback:
88109

89110
Audio playback

0 commit comments

Comments
 (0)