From Sismos México to Ready Together

I am Oscar Emilio Pérez Martínez, a Mexican mobile engineer. For more than ten years, I have built products across Android, iOS, and the services that support them—including Sismos México, Sofie, and SOSMex.

What one million downloads taught me—and what they did not

Sismos México has exceeded one million cumulative downloads in the project’s historical metrics. Its current public Google Play listing shows more than 500,000 installs. Both figures matter, but they describe different measurements and should not be collapsed into one claim.

That reach taught me that people value timely, understandable earthquake information. It did not prove that a household knows its meeting point, has assigned critical responsibilities, or can coordinate a shared response. Information and preparedness are related, but they are not the same product problem.

Venezuela renewed the urgency

The earthquakes in Venezuela during 2026 made that gap feel more urgent. They reinforced the need to help households prepare across places with different institutions, infrastructure, language, and connectivity—not by importing one country’s protocol into another, but by making coordination easier to practice.

This is motivation, not marketing evidence. I will not use real earthquakes, casualties, or recent trauma to create fear, and Ready Together does not claim it could have prevented specific harm.

Colombia clarified the product boundary

On August 10, 2026, the Servicio Geológico Colombiano reported a magnitude 7.4 earthquake near San José del Palmar, Chocó. The official facts were available and attributable. That is valuable—but reproducing a national catalog is not the product I want to build.

The product question begins after the report: why does this event matter to the people and broad areas a private circle chose, who has responded, and what responsibility is still unclear? Colombia helped turn that boundary into a concrete, testable engineering slice.

The missing tool is coordination

Authorities publish guidance. Earthquake apps explain what happened. Messaging apps help people communicate. A written plan records an intention. A household can combine all of them with a timer and a checklist, but the coordination burden remains with one person.

Ready Together is exploring the missing layer: bring the relevant people into one private practice, give each person an explicit responsibility, begin together, retain reviewed instructions when connectivity degrades, and reveal one factual gap afterward.

Why Ready Together starts with a circle

Ready Together explores a private-circle model. A circle chooses broad areas that matter, keeps responsibilities visible, and can practice a shared sequence before a real event. When reported earthquake information is relevant to those selected areas, the product can provide context and open a limited check-in. It is not early warning and it does not replace official guidance or emergency services.

The product also treats drills as product interactions, not as proof of safety. A shared report can record what the room confirmed and identify one thing to improve. It cannot certify that anyone is safe or that a household is prepared.

What exists today

The exact label for Ready Together today is local prototype. Android and iOS interfaces exist in a Kotlin Multiplatform project. The synchronized-practice flow has automated coverage, while the final physical Android–iPhone Gate A remains open. The private Firebase circle and check-in experience is not publicly deployed, and the app is not released in either store.

A separate public Render service exposes a bounded, read-only earthquake feed for reviewed areas. That backend slice should not be mistaken for the private Ready Together product being available in production.

Why I am writing before launch

Building in public is useful only if it makes uncertainty visible. The goal is not to narrate every commit or turn architecture into marketing. It is to show the decision, the evidence, the limitation, and the next question without upgrading a prototype into a finished product.

My experience explains why I am investigating this problem. It is not evidence that Ready Together works. The next meaningful evidence must come from reproducible product behavior and, later, carefully documented physical testing—not from a founder story.