The story · part 5 of 5
⛵ By the sea: your app sets sail.
In Gaulish, are-mori means "by the sea". So everything that leaves the village goes over the water.
The story
On the village shore a sloop lies ready. Scan the QR code and you go aboard: the sloop carries your hut to your phone. When Panoramisk brews a new version, the sloop moors again by itself.
When your app is ready for the world, the shipyard builds a big ship. First a sea trial with your testers via TestFlight, then the crossing to the App Store or Google Play. And whoever truly arrives will one day get a menhir next to the hut, as a standing stone.
⛵
Sloop
Armori.ca Go
⚓
Shipyard
The builder
🧭
Sea trial
TestFlight
🌊
Crossing
The stores
🗿
Menhir
A release (plan)
What works today
Available• Armori.ca Go: scan the QR code and your app runs natively on your phone.
• A new version loads by itself; every package of Expo SDK 58 is on board.
• Requests to /api go from the phone to your app's API.
• Builds for TestFlight, .apk and .aab, on a builder (a Mac).
• A queue and a live log in the browser; the full log is kept.
• Build number and bundle ID filled in; Apple credentials per workspace, an upload key per Android app.
Still in the cauldron
Plan• Harbour with berths: which version is where.
• High and low tide, a flag on the mast, pull to refresh with a soft "plop".
• Moored sloop: the last version keeps working offline.
• Not on the sloop: see up front which package isn't in Go.
• The label on the bottle: store texts and screenshots by Panoramisk.
• The tasting, a shopping list, a dry run and a stress test before the crossing.
• Harvest ("What's new"), cargo list and seal on every build.
• The menhir for a real release; "Rejected? Let Panoramisk read it".
• A heads-up on your phone when a build is done, and the queue with departure times.