Quality, Security and Privacy in Every Release
When someone installs one of our apps, they are trusting us with their time, their device and often their personal data. Our development standards exist to make sure that trust is never misplaced.
Quality assurance at every stage
Testing is not a step at the end of a project; it runs through the whole of it. Code is reviewed by another developer before it is merged, automated tests catch regressions, and every release is checked by hand on a range of real devices and Android versions before it reaches users.
Security by default
We follow industry-standard practices for building secure apps: encrypted connections, careful handling of credentials and keys, keeping third-party libraries up to date, and giving each part of the system only the access it needs. Security is considered when a feature is designed, not patched on afterwards.
Collect less, protect more
The safest data is data you never collect. We only ask for the permissions and information an app genuinely needs to work, explain why we need them, and protect what we store. Our apps follow the privacy requirements of the Google Play and Apple App Store platforms.
Listening after launch
No test suite catches everything. We monitor crashes and errors in real time, and user reports go straight to the team responsible for that app, so problems are found and fixed quickly.
Quality and security rarely make headlines when they are done well. That is the point: our users should simply be able to rely on our apps, every time they open them.