Custom Application Development
XGameDev develops applications for learning, fitness, construction and interactive 3D workflows. Work directly with Jacques and Melanie on a defined product, a subsystem alongside your team or improvements to an existing application.
NoMeLoMe: application, content delivery and supporting systems
What we build for your users
We turn a user task into working screens, interactions and supporting systems. The scope can include a Unity client, content libraries, accounts, APIs, data storage and administration tools. We connect those parts so the application and backend agree on how information moves and who can change it. Unity suits much of our interactive 3D and cross-platform work; lighter HTML5 can suit browser activities. We assess the interaction, devices and existing systems before choosing the delivery approach.
Planning the first app build
Describe the task
Tell us who uses the application, what they need to do and which systems it must connect to.
Agree a first milestone
We identify technical unknowns and define a working example, responsibilities and acceptance checks.
Review working software
Review the agreed features through usable builds, including client behaviour and connected services.
Prepare delivery
Test target environments and agree releases, source handover, documentation and support responsibilities.
NoMeLoMe’s content app and backend
For NoMeLoMe, we built a Unity app for animated books, puzzles, music and video. We also built the backend APIs and the systems that manage and process the media.
See our NoMeLoMe projectQuestions about commissioning an app
What should we send for an app estimate?
Share a sample workflow, the intended platforms and the systems the app must connect to. Sample data or content helps us scope an unfamiliar interaction before estimating the full build.
Can you improve an existing app?
Yes, subject to reviewing the source, licences and current build. We can own a defined feature or investigate a fault alongside your developers.
Do we need a finished specification?
No. A short workflow description and representative content can start the discussion. We then agree scope, responsibilities and what the first build must demonstrate.
Who owns and maintains the software?
Source access, licensed assets, accounts and handover belong in the scope. Hosting, operational responsibilities and ongoing maintenance need an agreed arrangement.
Bring us the workflow
Send the audience, main task, target devices and any existing software or data. Include a timeline and budget range if known.