Define the role of the app
The app may set up connectivity, pair a device, manage child profiles, select content, control volume, review battery status, configure bedtime behavior or deliver firmware updates. Not every product needs every feature. A focused first release should solve the essential parent and device tasks with as little friction as possible. The team should also decide which functions remain available if the app or cloud service cannot be reached.
Design onboarding as one system
Parents experience packaging, instructions, power-on behavior, lights, spoken prompts, phone permissions, account creation and Wi-Fi setup as one journey. If these elements use inconsistent language, onboarding becomes support work. Prototype the complete sequence early, including wrong passwords, unsupported networks, interrupted pairing and second-device setup. The toy should communicate status in a way that matches the app screen and printed instructions.
Align firmware, APIs and mobile releases
Device commands, event names, firmware versions and API responses require clear contracts. Teams should maintain a test matrix covering supported phones, operating systems, network states and device versions. Update behavior needs recovery rules so a child’s toy does not become unusable after a failed transfer. Development responsibilities may sit with different organizations, making interface documentation and shared acceptance tests essential.
Plan privacy and parental control
Connected toys can involve voice, identifiers, usage data and child profiles. The customer should define what data is collected, why it is needed, where it is processed, how long it is kept and how parents can control it. Privacy and security decisions belong in product architecture and legal review, not only in a policy page. Minimize data by default and make recording or connected states understandable to the parent and child.
Test with production-intent hardware
App demonstrations can appear successful while the final toy has weaker antennas, different microphones, slower power-on or changed buttons. Validation should use production-intent electronics inside the actual plush structure. Test repeated setup, factory reset, account transfer, network loss, low battery, long conversations and firmware updates. The same configuration used for certification and pilot production should be traceable through revision control.
Experience from international programs
The Germany AI plush doll and companion app team project began in July 2026, entered certification work in September 2026 and covers more than 2,000 units for the EU market. The US ESP32 AI plush and app project began in February 2026 and exceeds 10,000 units. Joy coordinates customer requirements and milestones with the wider project team rather than presenting these shared projects as individual work.
Frequently asked questions
Questions buyers ask before development
Do you build iOS and Android apps?
App scope and development responsibility are defined per project; the physical product, firmware and app interfaces are coordinated together.
Can the customer use an existing app?
Possibly, if its device protocol, onboarding and update requirements fit the new product.
Does every AI plush toy need an app?
No. An app should exist only when it provides necessary setup, control, content or support value.