Blog
Timmy's blog: the technology behind the app
Here I write down the technical decisions behind Timmy, how I think about security questions, and why some app boundaries are intentional.
- Security analysis, architecture, and product decisions sorted by topic
- Links between technical background and parent guides
- Concrete sources and code references instead of trust slogans
From product thinking to architecture
Start with product and development posts
These posts explain how Timmy is built, why the browser companion exists, and which product decisions shape daily use.
Then read security and architecture
Technical posts explain how pairing, WebRTC, and the system architecture work behind the simple flows in the app.
Switch to guides for parent questions
When technical topics become practical checks or buying criteria, the guides continue from a parent perspective.
Use the blog for background and the guides for parent decisions. The two sections add to each other instead of repeating the same content.
The blog is no longer a plain chronology. It is sorted by topic, so you can start with product development, technology, or transparency and then move straight into matching guides.
Each section answers a different question: How is Timmy built? How does its security architecture work? Which privacy choices shape the app?
Product & development
How Timmy is built and why the product works the way it does
These posts cover the product side of Timmy: the development process, the browser companion, and the decisions that turn a technical idea into a usable family tool.
Building Baby Monitor Timmy with GitHub Copilot
How we built a privacy-friendly baby monitor with AI pair programming, from concept to production.
Read more →Using Timmy Web Companion in your browser
What the web version can do, why it needs the premium app, and how pairing, microphone access, and security work.
Read more →Technology & security
How Timmy secures connections, pairing, and media
This section contains the denser technical posts: WebRTC, signaling, secure pairing, and security incidents that make architecture choices easier to examine.
The Tech Behind Timmy
WebRTC, Firebase, and end-to-end encryption explained clearly.
Read more →How Timmy Pairs Securely
The algorithm behind the verification number and why MITM attacks are detected.
Read more →What the Meari baby-camera security vulnerability shows – and why Timmy secures things differently
What the Meari incident shows about platform risk and how Timmy secures pairing, signaling, and WebRTC media differently.
Read more →Transparency & privacy
Why Timmy does not want to be a black box
These posts connect product principles with architecture: open source, privacy in the nursery, and why being understandable is not a marketing extra.
Why Baby Monitor Apps Should Be Open Source
Trust starts with being able to look. Why we make the code public.
Read more →Use the guides when you want practical checks
For permissions, secure pairing, or internet baby monitors, the guides are the direct next step.
Open the guides →