You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the iOS item of a three-part request (#647 Android, #648 iOS, #649 HarmonyOS).
Triaged on be48393b. Not ready to start: the issue carries no technical choice and no first slice, and it is one of three (Android #647, iOS #648, HarmonyOS #649) that need the same decision.
What the owner has to pick before an agent can move:
Route: PWA on the existing DSH Web GUI (fastest, no store, push via the browser), one cross-platform app (Flutter / React Native), or native per platform. The repo already serves a local Web GUI, so the PWA route is the only one that can be sliced small.
Order and scope: which platform first, and whether the first slice is "usable on a phone" (responsive layout, safe-area, the composer) or "installable + push + remote approvals" as well.
Distribution: store listing vs TestFlight/self-signed vs browser install — each has different requirements and none is an agent decision.
Until those are answered this stays needs-info. Once they are, the first slice can be written as agent-ready with a concrete acceptance (for example: the Web GUI opens on a phone, the sidebar and composer are usable at 390 px, manifest.webmanifest + display: standalone validate, and a test pins the responsive breakpoints) — that is a real issue I can open on the owner's word, separately from this roadmap item.
needs-human. This is the iOS item of one three-part request (#647 Android, #648 iOS, #649 HarmonyOS) and it needs one decision, not three: no technical choice exists in the issue, and the choice is the same for all of them.
What is missing, named:
the stack decision — PWA on the existing web GUI (cheapest, ships with the web build), a cross-platform framework (Flutter/React Native), or native. The HarmonyOS item adds one constraint: HarmonyOS NEXT cannot run an APK, so a native-Android route does not cover it.
the distribution decision — App Store / TestFlight / self-signing / no store at all (PWA).
What unblocks it: the owner picks a stack and a distribution route once, in #647. Then the three issues get that route written into their acceptance and the first slice (#647) becomes agent-ready; the other two stay blocked behind it by design.
Decision recorded (owner, 2026-10-25): PWA first. A native iOS client is not planned now — the mobile route is the PWA, which ships with the web build and also covers HarmonyOS NEXT (no APK needed). Native, TestFlight/App Store and self-signing wait until there is real user volume.
That does not make this a duplicate of #647 — it is the item that would be reopened when the PWA stops being enough, and its three questions (stack, notifications, distribution) are still the right ones then. Keeping it needs-human and open so the request is not lost, with nothing for a dev to start.
What would reopen it: a phone-side need the PWA cannot meet (background push on iOS, deep OS integration) or an owner decision to ship to a store.
Activity
Birfy commentedon Oct 23, 2026
This is the iOS item of a three-part request (#647 Android, #648 iOS, #649 HarmonyOS).
Triaged on
be48393b. Not ready to start: the issue carries no technical choice and no first slice, and it is one of three (Android #647, iOS #648, HarmonyOS #649) that need the same decision.What the owner has to pick before an agent can move:
Until those are answered this stays
needs-info. Once they are, the first slice can be written asagent-readywith a concrete acceptance (for example: the Web GUI opens on a phone, the sidebar and composer are usable at 390 px,manifest.webmanifest+display: standalonevalidate, and a test pins the responsive breakpoints) — that is a real issue I can open on the owner's word, separately from this roadmap item.Birfy commentedon Oct 25, 2026
Written-by: Triage
needs-human. This is the iOS item of one three-part request (#647Android,#648iOS,#649HarmonyOS) and it needs one decision, not three: no technical choice exists in the issue, and the choice is the same for all of them.What is missing, named:
What unblocks it: the owner picks a stack and a distribution route once, in
#647. Then the three issues get that route written into their acceptance and the first slice (#647) becomesagent-ready; the other two stay blocked behind it by design.Birfy commentedon Oct 25, 2026
Written-by: Triage
Decision recorded (owner, 2026-10-25): PWA first. A native iOS client is not planned now — the mobile route is the PWA, which ships with the web build and also covers HarmonyOS NEXT (no APK needed). Native, TestFlight/App Store and self-signing wait until there is real user volume.
That does not make this a duplicate of #647 — it is the item that would be reopened when the PWA stops being enough, and its three questions (stack, notifications, distribution) are still the right ones then. Keeping it
needs-humanand open so the request is not lost, with nothing for a dev to start.What would reopen it: a phone-side need the PWA cannot meet (background push on iOS, deep OS integration) or an owner decision to ship to a store.