Two import sources
Photos with usable location and time metadata can be brought together with a Google Timeline export. The app does not claim continuous tracking without the user importing data.
ORBIT DIARY
See a journey
as a whole route.
An iOS prototype that brings imported photos and Google Timeline exports into a globe-based timeline and a short recap video.
MVP core implemented
Local journey assembly
Place, time, and imagery assembled into one route.
Orbit Diary imports a user’s own travel records locally, aligns them on a globe-based timeline, and prepares a short recap from the reviewed journey.
- 01 · ImportPhotos and a user-provided Google Timeline export
- 02 · AlignTime and location data into a journey sequence
- 03 · ReviewGlobe view and timeline for checking the route
- 04 · RecapA short rendering built from the reviewed trip
Import, review, and render
Orbit Diary treats location history as user-provided input that needs inspection before it becomes a story.
Route analysis
The prototype removes implausible points, handles gaps, identifies stays and trip segments, and retains uncertainty where the data is sparse or low confidence.
Three globe themes
Realistic, flat, and dotted globe themes use the same reviewed route. A recap renderer turns it into a shareable video rather than a live surveillance view.
From records to recap
A journey is built only from sources the user chooses to import.
-
01
Import sources
Select photos and, if wanted, a Google Timeline export.
-
02
Review the route
Inspect stays, segments, and gaps before creating a visual recap.
-
03
Choose a theme and export
Pick a globe theme and produce a recap video from the reviewed route.
Illustrative workflow
- A traveler imports a selected trip’s photos and a timeline export.
- Orbit Diary separates a long data gap from an actual trip segment.
- The traveler chooses the dotted globe theme and exports a recap.
Development workflow
Codex supports development and verification, while route and photo data stay within the product’s import flow. Claude Code is being evaluated for selected workflows.
Inputs: route rules and failures
The work uses the import contract, analysis rules, rendering modules, and failure logs such as sparse location data or long gaps.
Work: pipeline and tests
Parsing, route analysis, and globe rendering remain separate, with tests for synthetic trajectories, edge cases, and renderer smoke paths.
Value: an honest recap
The resulting experience distinguishes a gap from a path and shows that the recap is built from reviewed records, not inferred surveillance.
The current prototype does not call the Claude API. Other Claude API ideas will be considered only after Findoc’s planned evaluation.
Questions at this stage
Does Orbit Diary track a user all the time?
No. It works from photos and Timeline exports the user chooses to import. It does not claim always-on tracking.
Is the visual output fully verified on devices?
Not yet. Core behavior is implemented, while current visual and physical-device checks remain before release.
Product enquiries