Luanti on mobile content (#107)

content/mobile/_index.md

@@ -0,0 +1,35 @@
+---
+title: Luanti on mobile devices
+bookCollapseSection: true
+aliases:
+- /Luanti_on_Android
+---
+
+# Luanti on mobile devices
+
+Luanti supports mobile devices and can be played using a touchscreen.
+
+If you're developing a game or mod, you can follow [this advice](/mobile/improving-games-and-mods-for-mobile) to make it more usable on mobile.
+
+## Android
+
+There is an official Android version. It's available on the [Luanti website](https://www.luanti.org/downloads/), on [Google Play](https://play.google.com/store/apps/details?id=net.minetest.minetest) and on [F-Droid](https://f-droid.org/packages/net.minetest.minetest/).
+
+Traditionally, the Android version only supported the touchscreen controls. Starting with version 5.10.0[^1], the desktop controls also work out of the box if you connect mouse and keyboard via bluetooth, without any special configuration required.
+
+Useful resources:
+
+- [Accessing Android Data Directory](/mobile-support/accessing-android-data-directory)
+
+Please do not download unofficial Luanti builds from the Google Play and any other app store. The builds found there may contain excessive adverts or spyware. They may be distributed under proprietary terms, without the source code, which makes them illegal to develop. They may be old or unsupported.
+
+## Linux phones
+
+You can also play Luanti on Linux phones. Starting with version 5.9.0[^2], Luanti should work on Linux phones out of the box, without any special configuration required. However, Luanti may work better on Linux phones if you compile it yourself with `-DUSE_SDL2=TRUE`. All official release builds have been compiled with `-DUSE_SDL2=FALSE` so far.
+
+## iOS
+
+There is no iOS support due to legal uncertainties and lack of developer time. While the "MultiCraft" fork of Luanti supports iOS, it contains advertising and is still based on the outdated engine version 5.4.1, so it isn't recommended.
+
+[^1]: See PR [#14542](https://github.com/minetest/minetest/pull/14542) and its various predecessors.
+[^2]: See PRs [#14075](https://github.com/minetest/minetest/pull/14075) and [#14400](https://github.com/minetest/minetest/pull/14400).

content/accessing-android-data-directory.md → content/mobile/accessing-android-data-directory.md

@@ -2,6 +2,7 @@
 title: Accessing Android Data Directory
 aliases:
 - /Accessing_Android_Data_Directory
+- /accessing-android-data-directory
 ---
 
 # Accessing Android Data Directory

content/mobile/improving-games-and-mods-for-mobile.md

@@ -0,0 +1,46 @@
+---
+title: Improving games and mods for mobile
+---
+
+# Improving games and mods for mobile
+
+The mobile platform is different from the desktop platform. You can't develop a Luanti game for desktop and expect it to work on mobile without any adjustments. While Luanti needs to improve support for mobile by adding more mobile-specific features to the Lua API, that's not enough for mobile players to have a good experience. In the end, it will always be up to games and mods to use these APIs.
+
+All games and mods uploaded to ContentDB are available on Android and all servers can be joined on Android, so you will have some mobile players either way.
+
+If you want to improve mobile support in your game or mod, the most important thing to do is testing it on mobile. Play for some time, try doing different things and see what works and what doesn't. This page lists some common problems and offers solutions.
+
+## Touch controls: It's impossible to hold the place button / right mouse button
+
+In the touch controls, a long tap corresponds to pressing and holding the dig button and a short tap corresponds to briefly pressing the place button.
+
+This works well when only digging and placing nodes, but not in other scenarios. Some actions require the player to hold the place button, for example shooting with a bow or eating food in Minecraft-like games. Some actions require the player to be able to press the dig button very quickly, for example throwing grenades in [Capture the Flag](https://content.luanti.org/packages/rubenwardy/capturetheflag/).
+
+Luckily, it's possible to customize the meaning of long and short taps using the `touch_interaction` field in item definitions. As a solution for the cases described above, you can add the following line to your item definition:
+
+```lua
+touch_interaction = "short_dig_long_place",
+```
+
+This feature is available since engine version 5.9.0, older versions ignore it.
+
+## Android: Formspec text fields without a separate submit button cannot be submitted
+
+On desktop, you can submit text fields in formspecs by pressing the `Enter` key, so you don't necessarily need a separate submit button.
+
+On Android, tapping a text field will open a text input dialog with the screen keyboard. When the user taps `Enter`, it's not possible for Luanti to distinguish whether the user actually wants to press `Enter` or whether they just want to close the dialog. By default, tapping `Enter` only closes the text input dialog without emitting an `Enter` keypress. This means it's not possible for Android users to submit text fields without a submit button.
+
+![](/images/improving-games-and-mods-for-mobile/android-text-input-dialog.jpeg)  
+_The Android text input dialog_
+
+Available solutions:
+
+- Use the `field_enter_after_edit[]` formspec element on the text field
+
+  If this is set to true for a specific text field, an `Enter` keypress will be emitted after closing the text input dialog. This is used by e.g. the server list search field on the "Join Game" tab of the main menu.
+
+  This formspec element is available since engine version 5.8.0, older versions ignore it.
+
+- Add a submit button next to the text field
+
+  This also works, but is worse than `field_enter_after_edit[]` as the user needs to do two taps instead of one. It may also still be confusing for the user ("I already pressed `Enter`, why didn't anything happen?"). Ideally, you would add both `field_enter_after_edit[]` and a submit button.