Mobile Apps en Warsaw
How we work in Warsaw
The API contract is agreed and versioned
Which fields each call returns, what is optional and what can never be missing, documented and with a test environment to work against. A breaking change ships as a new version with notice, never replacing the previous one on the same day. Plus a short list of what the app does when the server does not answer, which is the case that always gets discovered in production.
A published app is not fixed in five minutes
On the server a bug is corrected and deployed. In an installed app you have to submit a version, wait for store review and trust that people update. That asymmetry is the real reason behind every rule above, and it is better understood before you need it.
Who looks first when nobody knows which side it is on
A written triage rule: whoever gets the alert reproduces the failure and decides the side with the trace in front of them. If it is not clear after a while, both sides look together instead of handing it back. Without that rule, an ambiguous bug travels between two teams for two days.
Your team keeps the signing keys
App Store Connect and Google Play accounts in your company's name, and the signing certificate in your own secret store. Losing a signing key is a serious and expensive thing to undo: we would rather not be the ones holding it. We sign and publish with the access you give us while the contract lasts, and the procedure is written down so somebody else can repeat it.
Answering your questions
What people ask us about Mobile Apps in Warsaw.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Mobile Apps: stack, process, use cases and FAQs