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
**Planned:** broad device-verified background geofence reliability, elevated (Shizuku) execution, Termux script dispatch, a visual flow authoring editor, and richer plugin UX. See [ROADMAP.md](ROADMAP.md).
22
22
23
-
> **Status:** the current source version is `0.2.65`. Device-evidence claims (location/calendar/sun) are single-device API 36 data points on `SM-S938B`, not broad background-geofence reliability guarantees. The latest polish pass improves IME handling, compact small-screen bottom navigation with a More menu, variable and scene-element deletion safety, saveable editor/context/template/scene-element state, numeric form keyboards, larger day-token touch targets, and accessibility roles for widget/flow/form switch targets.
23
+
> **Status:** the current source version is `0.2.66`. Device-evidence claims (location/calendar/sun) are single-device API 36 data points on `SM-S938B`, not broad background-geofence reliability guarantees. The latest polish pass improves IME handling, compact small-screen bottom navigation with a More menu, squared-off navigation/FAB affordances, variable and scene-element deletion safety, saveable editor/context/template/scene-element state, scene-element nudge controls for non-drag movement, numeric form keyboards, larger day-token touch targets, and accessibility roles for widget/flow/form switch targets.
Copy file name to clipboardExpand all lines: RESEARCH.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Updated: 2026-06-15 (stricter release-polish pass; replaces previous research co
4
4
5
5
## Executive Summary
6
6
7
-
OpenTasker is a Kotlin/Compose Android automation app at source version 0.2.65 with a Room-backed profile -> context -> task -> action engine, 49 registered runtime actions, engine-handled flow control, FOSS LocationManager geofencing, Locale/Tasker plugin hosting, Tasker XML import, OpenTasker JSON transfer, Quick Settings/widget triggers, OEM battery guidance, and F-Droid/Play release checks. The repo's best trait is explicit failure behavior: unsupported privileged actions fail honestly, imports are review-gated, sensitive run-log data is redacted, destructive variable and scene-element deletion are visually confirmed, and prior high-risk guards remain in place.
7
+
OpenTasker is a Kotlin/Compose Android automation app at source version 0.2.66 with a Room-backed profile -> context -> task -> action engine, 49 registered runtime actions, engine-handled flow control, FOSS LocationManager geofencing, Locale/Tasker plugin hosting, Tasker XML import, OpenTasker JSON transfer, Quick Settings/widget triggers, OEM battery guidance, and F-Droid/Play release checks. The repo's best trait is explicit failure behavior: unsupported privileged actions fail honestly, imports are review-gated, sensitive run-log data is redacted, destructive variable and scene-element deletion are visually confirmed, and prior high-risk guards remain in place.
8
8
9
9
The highest-value direction is trust and scale before more action breadth. Existing roadmap items already cover target-SDK readiness, Android 17 audio gating, work/private-profile app automation, TalkBack accessibility, profile/task organization, action implementation tests, WorkManager resilience, diagnostics, Tasker XML export, scoped LAN cleartext, date/time templates, camera/mic privacy triggers, Wake-on-LAN, and optional BYO-key AI authoring.
10
10
@@ -60,7 +60,7 @@ Recent continuation passes found three additional non-duplicate gaps; v0.2.62 cl
60
60
- Target-SDK wording risk remains: live Google target-API pages checked on 2026-06-15 still publish the API 35 / August 31, 2025 requirement, not a public API 36 Play deadline. Target-36 code has shipped, but docs must not mark an unpublished deadline as verified.
61
61
- Android 17 audio risk remains: `MediaActions.kt` and TTS/sound code can run from background profiles while `AutomationService` uses `specialUse|location`; background audio hardening can fail playback or volume changes silently unless a valid foreground-service/while-in-use path exists.
62
62
- Work profile / Private Space risk remains: app-open contexts, package broadcasts, and app launch actions are package-name/current-profile based; no model currently records `UserHandle`, profile labels, hidden-profile state, or profile-local disclosure.
63
-
- Accessibility gap is narrowed but remains: action checkbox rows, profile/context form switches, widget task rows, and flow graph targets now expose better roles/state; numeric fields request numeric keyboards, small day-token controls meet 48 dp minimum height, and scene element edit/delete dialog state is restored from stable scene id/index state. A full TalkBack sweep and accessibility-checks instrumentation gate are still missing.
63
+
- Accessibility gap is narrowed but remains: action checkbox rows, profile/context form switches, widget task rows, flow graph targets, and the custom bottom navigation expose better roles/state; numeric fields request numeric keyboards, small day-token controls meet 48 dp minimum height, and scene element edit/delete dialog state is restored from stable scene id/index state with row-level nudge controls for non-drag movement. A full TalkBack sweep and accessibility-checks instrumentation gate are still missing.
64
64
- Action test gap is narrowed but remains: `core/actions/ActionGuardsTest.kt` now covers key network, URL, wait, ping, and Wake-on-LAN guards, while file, media, settings, app, notification, and download edge cases still need coverage.
65
65
- Network hardening gap closed in v0.2.62: `HttpPostAction` caps request bodies at 1 MB, uses fixed-length streaming, and keeps legacy `body` compatibility under the same cap.
66
66
- New supply-chain gap: `.github/workflows/build.yml` and `release.yml` consume tag-pinned actions (`@v4`), the build workflow has no explicit `permissions`, `gradle/verification-metadata.xml` is absent, and no Dependabot config is present.
Copy file name to clipboardExpand all lines: ROADMAP.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
# OpenTasker Roadmap
2
2
3
-
Source-backed product roadmap for OpenTasker v0.2.65 → v0.3.x. Reconciles current repo state with competitive research across Android automation apps, adjacent workflow engines, platform constraints (API 35–36), distribution policy, and dependency changelogs.
3
+
Source-backed product roadmap for OpenTasker v0.2.66 → v0.3.x. Reconciles current repo state with competitive research across Android automation apps, adjacent workflow engines, platform constraints (API 35–36), distribution policy, and dependency changelogs.
**Planning rule:** items marked "Now" must ship before the v0.3.0 public beta claim. Items already completed in 0.2.x are retained in the **Completed Backlog** appendix for traceability and explicitly removed from active tiers.
9
9
10
10
## Reconciliation note (2026-05-06 pass)
@@ -133,7 +133,7 @@ Key local constraints:
133
133
134
134
### N9 (2026.05.06) - Documentation truth pass post-v0.2.59
135
135
136
-
**Status:** Partially refreshed through v0.2.65: README, ROADMAP.md, RESEARCH.md, Gradle version values, F-Droid metadata gates, compact More-menu phone navigation, saveable editor/context/template/scene-element state, numeric keyboard hints, row-level switch semantics, and destructive variable/scene-element affordances now reflect the target-SDK-36/action-metadata and stricter UI polish passes. Older architecture and readiness docs still need a current-version truth pass before this item closes. [L14]
136
+
**Status:** Partially refreshed through v0.2.66: README, ROADMAP.md, RESEARCH.md, Gradle version values, F-Droid metadata gates, compact More-menu phone navigation, squared-off navigation/FAB affordances, saveable editor/context/template/scene-element state, scene-element nudge controls, numeric keyboard hints, row-level switch semantics, and destructive variable/scene-element affordances now reflect the target-SDK-36/action-metadata and stricter UI polish passes. Older architecture and readiness docs still need a current-version truth pass before this item closes. [L14]
137
137
**Description:** Refresh README, CLAUDE.md, ARCHITECTURE.md, IMPROVEMENT_PLAN.md, and FDROID_READINESS.md to reflect the current release. Restructure long status copy into skimmable feature lists where needed. Sync version strings, toolchain versions, workflow filenames, fdroid metadata, Gradle properties, ROADMAP, and CHANGELOG.
138
138
**Sources:** Local repo state [L1][L5], existing improvement plan [L7], dependency/release audit [L14].
139
139
**Category:** docs, dev-experience.
@@ -163,7 +163,7 @@ Key local constraints:
163
163
164
164
### X1 (2026.05.06) - Scene editor finishing pass
165
165
166
-
**Status:** Element creation/editing, drag-to-move, and scaled previewsshipped in v0.2.59. Resize handles, multi-select layout edits, alignment guides, and overlay launch (`SYSTEM_ALERT_WINDOW`) remain.
166
+
**Status:** Element creation/editing, drag-to-move, scaled previews, and row-level 1 dp nudge controls shipped through v0.2.66. Resize handles, multi-select layout edits, alignment guides, and overlay launch (`SYSTEM_ALERT_WINDOW`) remain.
167
167
**Description:** Add resize-handle drag, snap-to-grid + alignment guides, multi-select with bulk move/align/delete, then wire scene-launch action through the existing overlay-permission onboarding so a task can show a configured scene. Keep Android 15 background-FGS overlay restrictions in scope.
0 commit comments