# Port a PC game to mobile > The engine work is the easy part. Touch controls, small screens, short sessions, and thermal limits are what make or break the port. - URL: https://www.summerengine.com/port-pc-game-to-mobile - Keyword: port pc game to mobile - Related: https://www.summerengine.com/porting Porting a PC game to mobile means rebuilding the input, interface, and performance budget of a game you own for a phone or tablet. A shrunken desktop build with a virtual gamepad drawn over it is the most common way mobile ports fail. Four constraints drive every decision. Input becomes touch, which is imprecise and covers part of the screen with fingers. The screen is small, so dense UI becomes unreadable. Sessions are short and interrupted, so the game must save and resume constantly. Hardware runs in a thermal and battery envelope, so sustained frame rate matters far more than peak performance. Summer Engine exports desktop builds today, and iOS and Android builds need that platform's toolchain and signing (the Android SDK and a keystore, or a Mac with Xcode for iOS) and a pass on touch input. C++ and GDScript carry over, and C# is available in the desktop editor, though C# on mobile is still experimental in Godot 4 workflows. You own the project and pay no royalties on either platform. ## Redesign the controls, do not remap them Look at the verbs the game needs and find touch equivalents. Point and click adapts almost directly. Real time strategy needs a new selection model. Twin stick shooters need auto aim or a lock on. Precise platforming needs generous input buffering and coyote time. Simulation and management games often work better on a tablet than on a desktop. Add controller support for players who want it, but the game has to be complete with touch alone. ## Rebuild the interface for a small screen Desktop UI assumes a mouse, hover states, right click menus, tooltips, and dense information. None of that exists on a phone. Increase font sizes, enlarge hit targets to at least 44 points, remove hover dependent information, replace right click with long press, and split crowded screens into a small number of clear ones. Keep the main action area clear of where thumbs rest. Respect notches and safe areas on both platforms. ## Performance and download budgets Cut texture resolution to what is visible on a phone display, use compressed formats per platform, reduce draw calls, and simplify lighting and post processing. Measure sustained frame rate after several minutes, because throttling shows up late. Watch memory, since both platforms terminate apps that exceed budget. Keep the download small: iOS prompts before large cellular downloads, and Android install conversion drops as size grows. ## Session design and store expectations Mobile sessions are minutes long and get interrupted by calls and notifications. Autosave frequently, resume exactly where the player left, and make progress legible after a week away. Consider chunking long PC levels into shorter units. Then decide monetization deliberately: a premium price works on mobile but competes with free, and any in app purchase must go through Apple or Google billing for digital goods. ## FAQ ### Can I just add a virtual joystick to my PC game? It rarely works. On screen sticks are imprecise and cover the screen. Redesign the control scheme around taps, holds, swipes, and drags, and add assists where the original relied on precision. ### Which is easier to ship to first, iOS or Android? Android is faster to test because you can install a build on a phone immediately with no review. iOS has the stricter pipeline but a more consistent device range. Many teams develop on Android and submit to both. ### Will the same code run on mobile? The gameplay code largely does. C++, GDScript, and C# all work on mobile targets. What changes is input, UI, asset budgets, and lifecycle handling for suspend and resume. ### Do mobile players expect free to play? It is the dominant model, but premium mobile games do sell, especially ports with a known PC reputation. Decide early, because monetization design affects pacing and progression, not just the price tag. ### How long does a PC to mobile port take? Budget for the redesign rather than the build. Control scheme, UI rework, and performance passes usually take longer than making the engine produce a mobile binary. [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