Keep your mobile app or game working as iOS, Android and app store requirements change. XGameDev helps clients worldwide with software updates, bug fixes and store releases, including taking over existing projects. You don't need to know how your app was built to get in touch.
An app can need an update even when you aren't adding features. We review the project and agree which fixes, devices and release steps the work will cover.
Update the app for supported operating systems and test the parts your users rely on, including sign-in, saved progress, purchases, camera access and notifications where applicable.
Review and update the third-party software behind ads, payments, analytics and other features. We resolve integration and build problems, then test the affected behaviour.
Work through store notices, build requirements and privacy disclosures with you. Prepare test builds, submit agreed updates and respond to technical review feedback.
Investigate crashes, slow loading, unresponsive screens and device-specific faults. Reproduce the problem, make the fix and check it on the agreed devices.
iOS and Android change, third-party services retire older integrations, and the stores update their publishing requirements. An app that worked at launch can later develop compatibility problems or need changes before its next release.
For example, Google Play's target API requirements affect both update submissions and availability to new users on newer devices. Apple's third-party SDK requirements cover privacy information and signatures for listed software components. SDKs are the third-party software packages that add features such as ads, analytics or sign-in to your app.
We check the requirements that apply to your product and store accounts when planning an update. That includes checking what the app and its integrations actually do, so privacy disclosures reflect their behaviour.
Your original developer may have moved on, or your team may need help with a release it can't complete. Start with the app's store link and the problem you need to solve. Tell us about any store notice or deadline, even if you don't know the technical cause.
We review the available project files and build history, identify the software and services the app relies on, and confirm what we can support. If source code, signing access or a working build is missing, we explain how that affects the options before estimating changes.
A single repair or store update can be a defined piece of work. For a product that needs regular attention, we can agree ongoing support with a review schedule, priorities and availability that fit the app.
A mobile issue can start in a connected service. For Step Out Academy, our work covered the iOS and Android app alongside APIs, multiplayer sessions, QR links and augmented reality. The project included native build fixes and device behaviour that needed testing outside the editor.
If your app relies on accounts, shared data or a server, we include those dependencies in the initial review. Our backend and full-stack development service covers that work when it needs its own scope.
Planning a new game as well as maintaining an existing one? See mobile game development. For bringing an existing game to another platform, see game porting.
We've co-developed Zulu Chess with CCI NY, Blac Foundation and Pubbly since 2012. The project has evolved from a 3D game into a 2D multiplayer board game, with builds for iOS, Google Play and WebGL. It is a documented example of our work on an existing product over many years.
Read the Zulu Chess projectYes. Send the store link, describe the issue and tell us what project files or developer contact details you have. Our mobile experience includes Unity apps and games; we review the technology and source before confirming the work we can take on. You don't need to identify the engine or framework yourself.
Yes, subject to reviewing the project. We check source availability, dependencies, build instructions and account access before agreeing the work. If the original developer is available, a handover can help establish which version matches the app in the store.
Code changes normally need the original project source and permission to use it. Store releases also need appropriate access to your developer account and signing setup. If files are missing, we first assess what can be recovered and whether a rebuild is needed. Leave passwords and signing keys out of the initial enquiry.
Share the notice, deadline and affected platform so we can review the cause and scope the response. We can address technical issues and help prepare a resubmission. Apple and Google decide approval and review timing; we can't guarantee acceptance or restoration of a removed app.
We can scope a specific fix or release, or agree ongoing support for planned updates and recurring issues. The arrangement defines what we monitor, how work is prioritised and when support is available. New features and major upgrades need an agreed scope too.
The estimate depends on the app's condition, available source, age of its dependencies, required fixes and device test coverage. We review those details before estimating. A small store update can expose older build or plugin problems, so we explain any investigation needed first.
Send the app's store link, what needs attention and any deadline. If you aren't sure where to start, describe what your users are seeing. Jacques or Melanie will reply within one business day.