Driving education · United States
DMV Practice Test: DriveMaster
A structured practice companion for U.S. learner drivers studying road rules, traffic signs and permit-test topics.
Read product notesWe design and build iOS & Android apps for modern products.
APPME brings product strategy, interface design and mobile engineering together in one focused team. We turn useful ideas into dependable products people can understand and keep using.
iOSNative & Swift
AndroidKotlin & modern
Product designUI/UX & prototyping
Product strategyFrom idea to growth
Selected products
Software made for focused learning.
English learning · Children
Learn English by Coloring
A playful early-learning experience that helps children build English vocabulary through coloring, spoken words and short visual quizzes.
Read product notes
Creative learning · Children
Tiny Gallery: Coloring Book
A small offline coloring experience designed around simple controls, local profiles and on-device artwork.
Read product notesLatest engineering guides
Practical answers to specific product problems.
Android Offline Sync with an Outbox and WorkManager: Prevent Duplicate Writes
A practical design for local writes, durable delivery and server confirmation when a lost response could otherwise create the same result twice.
Android Passkey Account Recovery: Design the New-Phone Sign-In Journey
Plan credential management and recovery alongside passkey sign-in, with explicit account, session and new-device boundaries.
iOS Privacy Manifest SDK Audit: Review the Archive Before App Store Submission
A repeatable release review based on the distributed archive, dependency ownership and documented privacy behavior rather than a file-presence check.
Our point of view
Useful software begins with a clear problem.
A mobile product is more than a list of screens. It is a chain of decisions about audience, information, interaction, reliability and long-term maintenance. We make those decisions visible before they become expensive code.
Our work starts by defining the job the product must do. Design reduces friction, engineering protects the experience, and measurement shows what should improve next.
See how we workCore capabilities
One product team, three connected disciplines.
Product strategy
Define the audience, core use case, release scope and success signals before committing to a roadmap.
Interface design
Shape flows, content and interaction states that remain clear on real devices and in real-world conditions.
Mobile engineering
Build, test and release maintainable applications for iOS and Android, supported by dependable APIs.
Technology news
Current platform changes, translated into product decisions.
iPhone Duo makes adaptive iOS design a release requirement
Apple has released iPhone Duo development resources. The immediate task for product teams is to test live resizing, posture changes, multiple scenes and camera behavior—not simply add another screenshot size.
Read analysis →
Android 17 adaptive app migration guide for phones, foldables and tablets
For apps targeting API 37, Android 17 ignores legacy orientation and resizability restrictions on large screens. A portrait-only assumption can now become a runtime defect.
Read analysis →
Two Google Play requirements for 2027: memory quality and Zero-Tap Sign-In
Google Play has announced memory and code-optimization thresholds for February 2027 and a device-migration sign-in requirement for April 2027. Both belong on the product roadmap now.
Read analysis →Product field notes
Practical writing from the work around an app.
From idea to mobile release: a seven-stage working checklist
A practical way to move from an attractive idea to a testable, supportable mobile release without hiding the difficult decisions.
Native or cross-platform? Choose from product constraints
A decision framework for comparing native iOS/Android development with a shared mobile codebase—without treating the framework as the strategy.
Mobile analytics with less data and clearer purpose
How to design a useful event model, reduce unnecessary collection and keep product measurement aligned with store disclosures.
Trust through clarity
Who wrote it, why it exists and when it changed.
Every field note names its editorial owner, publication date and primary references. Our editorial policy explains how we review technical claims, use drafting tools and correct material errors.
Start with the problem