A model-rocket launch is the visible end of a much larger process: the vehicle must be documented, the site understood, conditions checked, hardware prepared, safety procedures followed, and the flight recorded well enough to learn from it.
A SwiftUI application concept covering rocket inventory, launch planning, site records, weather, safety checklists, legal zones, and post-flight logging.
The aim. Bring the scattered administrative and technical parts of a model-rocket launch into one clear mobile workflow.
01The problem behind the project
Josiah's rocket work showed that successful launches depend on more than the airframe: conditions, site rules, hardware, checklists, and records all matter.
The iOS app concept collects those fragments into a field companion. Rockets, launch locations, weather, legal and safety zones, checklists, and post-flight logs would share one workflow instead of living in separate notes and websites.
Hobby rocketeers, student teams, clubs, and supervisors may benefit. Safe operation depends on experienced adults, applicable rules, and launch-site authorization.
02How it took shape
The current artifact is a product specification and SwiftUI-oriented information architecture; no working application code is claimed.
The current artifact is a product specification and SwiftUI-oriented information architecture grounded in Josiah's earlier Horizon rocketry work. No working application code or validated field deployment is claimed.
Josiah derived the concept from hands-on model-rocketry experience and defined the intended field workflow.
The design is documented and grounded in a real prior rocket program, but it has not been implemented or user tested.
03What the project means now
The concept's safety boundary is essential. A checklist can improve preparation but cannot grant permission to launch, replace a range officer, interpret every regulation, or certify a vehicle. The first credible prototype would focus narrowly on preparation and evidence capture.
An app cannot certify safe flight or replace laws, range procedures, weather judgment, or qualified supervision.
A field tool should connect preparation, decision, and evidence without presenting its checklist as permission to launch.
Prototype the launch-day checklist and log first, using established safety codes and expert review.