docs(planning): Atomic Launcher — SearchLauncher × Atomic merge - #1252
Draft
joepio wants to merge 4 commits into
Draft
docs(planning): Atomic Launcher — SearchLauncher × Atomic merge#1252joepio wants to merge 4 commits into
joepio wants to merge 4 commits into
Conversation
Map how the Kotlin SearchLauncher shell and Atomic's Rust data plane can merge: uniffi/Android host (not Flutter rewrite), unified search projection, quick-create verbs, and a phased path from HTTP spike to Binder-backed on-device node. Co-authored-by: Joep Meindertsma <joep@ontola.io>
Add presentation layers: compact search rows, favorites pins, optional ambient peek, AppWidgets, and a warm data-browser PWA shell so Atomic tables/docs/chats feel like first-class apps without a Compose rewrite. Co-authored-by: Joep Meindertsma <joep@ontola.io>
Capture + unified find at the home bar are the merge's unique payoff; rich editing can stay an app. Add a decision test so we don't merge for wallpaper/widgets vanity. Co-authored-by: Joep Meindertsma <joep@ontola.io>
Intents/Binder already deliver ~80% (search + create at the home bar). Spell out what owning HOME uniquely buys vs a normal Atomic app, and what one-APK embed still buys over a two-APK API client — so we don't merge for the wrong reasons. Co-authored-by: Joep Meindertsma <joep@ontola.io>
11 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Exploration plan for Atomic Launcher: SearchLauncher × Atomic.
Full write-up:
planning/atomic-launcher.mdCore clarification (HOME ≠ merge)
Intents/Binder already get ~80%: search +
todo get breadat the home bar while SearchLauncher stays HOME and Atomic is a separate host APK (android-data-reuse).What owning HOME uniquely buys (no Atomic APK can polish into existence):
QUERY_ALL_PACKAGES, etc.)What one-APK embed still buys over Binder (the other ~20%):
Path: keep SearchLauncher as HOME → validate with Binder client (A) → embed
atomic_libin the launcher (B) when onboarding/latency/identity hurt → rebrand (C) later.No runtime code — planning only.