# Port a Unity game to Android > A Unity to Android port is a rebuild plus a Play Console release. Device spread and the signing keystore cause more delays than the code. - URL: https://www.summerengine.com/port-unity-game-to-android - Keyword: port unity game to android - Related: https://www.summerengine.com/porting Porting a Unity game to Android means rebuilding a game you own and publishing it to Google Play or another Android store. Summer Engine does not read Unity project files. Android is easier to reach than iOS and harder to test. Anyone can build and sideload an APK in minutes, and a Google Play developer account costs 25 USD once. The difficulty is the device range: thousands of chipsets, screen shapes, refresh rates, and driver quirks, from a flagship down to a budget phone with 3 GB of RAM. Summer Engine exports desktop builds today, and an Android build needs the Android SDK, a keystore for signing, and a pass on touch input. Code is C++ and GDScript, with C# available in the desktop editor, though C# on Android is still experimental in Godot 4 workflows. You keep the project and the revenue. ## Google Play requirements that block releases New apps and updates must be uploaded as an Android App Bundle, not an APK. Play enforces a minimum target API level that rises every year, so a build targeting an old SDK is rejected. 64 bit arm64 support is required. You must complete the Data safety form, declare any sensitive permissions, provide a privacy policy URL, and complete content rating questionnaires. New personal developer accounts also face additional testing requirements before production access. ## Keystore and app signing, the part people lose Every Android build is signed. Play App Signing holds the distribution key while you keep an upload key. Back up the upload keystore and its passwords somewhere you will still have them in five years. A lost upload key can be reset through Play support, but a lost key on a self distributed APK outside Play means you cannot ship an update to existing installs at all. Set this up before the first release, not after. ## Input, screens, and the back gesture Rework the controls for touch rather than drawing a gamepad on the screen. Support aspect ratios from 4:3 tablets to tall 20:9 phones, and respect display cutouts. Handle the system back gesture explicitly, since Android users expect it to close menus and eventually exit. Handle focus loss on calls and notifications by pausing and saving. Support both 60 Hz and high refresh displays, and cap the frame rate when the battery is the constraint. ## Performance on the phone people actually own Pick a target device near the low end of your intended audience and test on it weekly. Budget textures with compressed formats, keep draw calls low, and watch sustained frame rate after five minutes rather than the first thirty seconds, since thermal throttling hits mid range phones hard. Measure APK or AAB size too. Download size affects install conversion more than most developers expect. ## FAQ ### Can Summer Engine open a Unity project for Android? No. There is no Unity importer. You rebuild the game in Summer Engine and bring over the textures, audio, models, and data you own. ### How much does a Google Play developer account cost? A one time 25 USD registration fee. Google then takes a revenue share on sales and in app purchases. Summer Engine charges no royalties. ### APK or AAB, which do I need? Google Play requires an Android App Bundle for new apps and updates. An APK is still fine for direct downloads, itch.io, or sideloading outside Play. ### Does C# work on Android? C# is available in the desktop editor alongside C++ and GDScript, but C# on Android is still experimental in Godot 4 workflows. GDScript or C++ is the safer choice for gameplay code you plan to ship on Android. ### Can I ship the same rebuild to iOS later? Yes, the Android rebuild can be the base for an iOS build, with platform specific input and store work on top. An iOS build needs a Mac with Xcode and signing, and Summer also exports desktop builds from the same project. [Start the rebuild](https://www.summerengine.com/download) --- ## Machine-readable resources - Site index for agents: https://www.summerengine.com/llms.txt - Full inlined content: https://www.summerengine.com/llms-full.txt - Porting catalog: https://www.summerengine.com/llms-porting.txt - Structured catalog: https://www.summerengine.com/agent-catalog.json - Sitemap: https://www.summerengine.com/sitemap.xml - Developer resources: https://www.summerengine.com/docs