A planning session should be able to continue when the information it needs is already on the machine. For Aerlattice, that requirement shapes where the calculations run and how the working record is stored.
We are designing the desktop application around a local planning service and a workspace on the user’s computer. The map is one view of that workspace, alongside the route details, findings and timeline.
Keep calculation separate from presentation
Moving between a 2D plan and a 3D scene should not change the rules used to assess a flight. The interface needs to present the route and its findings while the same local engine performs the checks.
Separating those responsibilities also allows longer calculations to run away from the interface, so the user can continue inspecting the workspace while a check or route search completes.
Store enough to resume the work
Routes alone do not capture a planning session. Assessments, decisions and recordings need to remain connected to the project so someone can return to what was considered.
A local database provides that working record. Complete backups support recovery of the workspace, while project exports let a user retain or transfer a particular set of plans and decisions.
