During the September 19, 2026 earthquake drill, three families who use Sismos México joined our beta test and completed a practice with Ready Together. The three families had three to four members each, with 11 people participating in total. For us, that was an important step: families had used the app to practice together.
This field note was first published on September 13. We have updated it to include that later milestone while preserving the lessons from the earlier testing that helped us get there.
Ready Together is built around a small claim: a household should be able to practice a concrete scenario together, on separate phones, and learn one factual improvement afterward. That claim is easy to explain. Making every step support it has been much less easy.
The circle has to show all its people
A shared practice is not shared if one participant cannot tell who else is present or which responsibility belongs to whom. Runtime passes across two Android actors exposed missing or unclear member context and check-in states. That turned “the flow works” into a more demanding requirement: the group must remain legible while the event is happening.
The resulting work focused on member visibility, responsibility hierarchy, check-in convergence, and recovery after an invitation or notification path does not arrive as expected.
The first viewport has to earn trust
The earliest version could be completed, but completion was not the same as confidence. Mixed-language copy, an unclear empty state, first-load retry behavior, and a form-like presentation made the product feel less certain than the underlying coordination model.
Those observations became concrete fixes. We kept asking a simple question: if someone is seeing this screen for the first time, can they identify the next useful action without an explanation from the builder?
Offline is part of the product
A drill cannot depend on a perfect connection. The validation work exercised offline restart, retained local facts, reconnect, and reconciliation. The important behavior is not pretending that the network state does not exist. It is keeping known information visible, avoiding optimistic conclusions, disabling actions that cannot be confirmed, and making recovery explicit.
That changed how we describe the experience. Offline is not just a failure mode to hide behind a spinner. It is one of the states the product has to make understandable.
Three families practiced on September 19
Conversations with our community of earthquake enthusiasts helped shape the focus on preparation. On September 19, we tested the app with three beta families who use Sismos México. Each family had three to four members, with 11 participants in total. All three families completed a drill. It was a small, concrete result for the experience we had been building.
The earlier QA and UX work described above had focused on clarity: show the group, make the next action obvious, preserve known information when connectivity changes, and make the report useful. The September 19 milestone adds a family practice result to that development history.
What we know now
Three beta families completed a drill. Ready Together is now available on both Google Play and the App Store. Our next question is whether families return to practice and use what they learn to improve their household plans. Completing one practice is an encouraging start; it does not yet answer that question.
Ready Together helps people prepare and coordinate. It does not predict earthquakes, provide early warning, contact emergency services, or certify that a household is safe.
What did people notice in your product that changed the experience more than a new feature would have?
Please share the observation, the change it caused, and how you know the change helped.