Mobile Apps en Sydney
How we work in Sydney
A nine o'clock alert, but nine o'clock there
A notification scheduled "for nine" from a European server reaches the user at seven in the evening. The same goes for daily digests and reminders. It is calculated in the user's own time and everything is stored in UTC, which sounds obvious until you audit an app and find it has not been done.
Daylight saving runs the other way in each hemisphere
The gap with Madrid is eight hours for most of the year, but not always: each hemisphere moves its clocks in different months and there are stretches where it is nine or ten. An offset hard-coded into the source breaks twice a year. It is solved with named time zones, never with a number.
The Australian store listing and the accounts, in your name
App Store Connect and Google Play under your company's name, with the Australian store listing and prices set per territory in Australian dollars. It is the difference between owning an app and borrowing one, and at this distance getting it back later is not an afternoon of paperwork.
A test build every night
We close our day by pushing a build to your testers. They use it through their morning, leave their comments and the bugs they found, and that is the first thing we open when we start. One full cycle per calendar day, without anyone having to log on outside their own hours.
Answering your questions
What people ask us about Mobile Apps in Sydney.
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