utilities/Logbook
Watch
1
0
Fork
You've already forked Logbook
 0
Code Issues 18 Pull requests Projects Releases 2 Packages Wiki Activity Actions

Decision: confirm Kotlin + Jetpack Compose stack #5

New issue
Closed
opened 2026-07-23 14:46:23 +02:00 by cloudbot · 1 comment
cloudbot commented 2026-07-23 14:46:23 +02:00
Collaborator
Copy link

Decision #5 — confirm the Kotlin + Jetpack Compose native stack, and pick the HTTP client.

The design doc assumes this stack (from the "native Android UI template sheet" framing) but flags it for confirmation, because it's the foundation the whole project scaffolds on.

Assumed stack (§11)

  • Kotlin + Jetpack Compose — native UI.
  • WorkManager — debounced/background sync.
  • Room — offline cache.
  • Android Keystore — per-user Outline API key storage.
  • Retrofit or Ktor — the Outline REST client (unresolved).

Secondary decision: Retrofit vs Ktor

  • Retrofit — the Android default; annotation-based, huge ecosystem, trivial to wire with Moshi/kotlinx-serialization and OkHttp. Best-understood, least-surprise choice.
  • Ktor client — Kotlin-first, coroutine-native, multiplatform-ready, more flexible for custom request shaping. Slightly more setup, smaller Android community.

What to decide

  1. Confirm Kotlin + Compose (and the WorkManager/Room/Keystore choices).
  2. Choose Retrofit or Ktor.

Blocks: project scaffolding (M1) — nothing can start until the stack is fixed.

Recommendation: confirm Kotlin + Compose, and use Retrofit + OkHttp + kotlinx-serialization. The Outline API is a plain REST surface (§12) with no multiplatform requirement, so Retrofit's maturity and lower setup cost win; Ktor's advantages don't pay off here.

Source: Solution Design — Family App v1 §11 (doc vpBNbG4TsV), decision §13 #5.

**Decision #5 — confirm the Kotlin + Jetpack Compose native stack, and pick the HTTP client.** The design doc *assumes* this stack (from the "native Android UI template sheet" framing) but flags it for confirmation, because it's the foundation the whole project scaffolds on. ### Assumed stack (§11) - **Kotlin + Jetpack Compose** — native UI. - **WorkManager** — debounced/background sync. - **Room** — offline cache. - **Android Keystore** — per-user Outline API key storage. - **Retrofit *or* Ktor** — the Outline REST client (unresolved). ### Secondary decision: Retrofit vs Ktor - **Retrofit** — the Android default; annotation-based, huge ecosystem, trivial to wire with Moshi/kotlinx-serialization and OkHttp. Best-understood, least-surprise choice. - **Ktor client** — Kotlin-first, coroutine-native, multiplatform-ready, more flexible for custom request shaping. Slightly more setup, smaller Android community. ### What to decide 1. Confirm Kotlin + Compose (and the WorkManager/Room/Keystore choices). 2. Choose Retrofit or Ktor. **Blocks:** project scaffolding (M1) — nothing can start until the stack is fixed. **Recommendation:** confirm Kotlin + Compose, and use **Retrofit + OkHttp + kotlinx-serialization**. The Outline API is a plain REST surface (§12) with no multiplatform requirement, so Retrofit's maturity and lower setup cost win; Ktor's advantages don't pay off here. **Source:** Solution Design — Family App v1 §11 ([doc vpBNbG4TsV](https://outline.marquezkeenan.family/doc/solution-design-family-app-v1-vpBNbG4TsV)), decision §13 #5.
ben commented 2026-07-23 17:44:26 +02:00
Owner
Copy link

I don't have a strong opinion on the stack. To define the requirements very clearly - text entry, and button interactions, must feel native and super fast and responsive.

I don't have a strong opinion on the stack. To define the requirements very clearly - text entry, and button interactions, must feel native and super fast and responsive.
ben closed this issue 2026-07-23 17:44:26 +02:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.1.0
v1.0.0
Labels
Clear labels   
bug
Something isn't working

  
chore
Tooling, scaffolding, maintenance

  
feature
New feature or capability

  
spike
Open question / research / decision to resolve

  
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Reviewed
Confirmed
 Issue has been confirmed

  
Reviewed
Duplicate
 This issue or pull request already exists

  
Reviewed
Invalid
 Invalid issue

  
Reviewed
Won't Fix
 This issue won't be fixed

  
Status
Abandoned
 Somebody has started to work on this but abandoned work

  
Status
Blocked
 Something is blocking this issue or pull request

  
Status
Need More Info
 Feedback is required to reproduce issue or to continue work

No labels
bug
chore
feature
spike
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#13 Scaffold Android app (Kotlin + Compose)
utilities/Logbook
#16 Core module & dependency setup
utilities/Logbook
Reference
utilities/Logbook#5
No description provided.