Skip to content

feat: add Android ongoing notification support#129

Merged
V3RON merged 3 commits intomainfrom
feat/android-ongoing-notifications
Apr 10, 2026
Merged

feat: add Android ongoing notification support#129
V3RON merged 3 commits intomainfrom
feat/android-ongoing-notifications

Conversation

@V3RON
Copy link
Copy Markdown
Contributor

@V3RON V3RON commented Apr 10, 2026

Summary

  • add support for rich Android ongoing notifications, including progress updates, actions, and remote updates
  • expose a server-side rendering API so apps can prepare Android ongoing-notification payloads outside the app runtime
  • expand the example app and documentation to cover setup, testing, and managing ongoing notifications end to end

User Impact

  • Android apps can now present persistent, richer notification experiences for flows like delivery tracking, rides, workouts, or other live status updates
  • teams can generate notification payloads on the server and send them through their push provider for background updates
  • developers have clearer docs and example flows for integrating, testing, and operating Android ongoing notifications

V3RON added 3 commits April 10, 2026 11:55
Add the Android ongoing notification flow across the example app, runtime APIs, and server rendering so apps can render, update, and remotely manage rich ongoing notifications. This also documents the server-side payload renderer and removes the example Firebase Android config from the Expo app config.
@V3RON V3RON merged commit 14d4fa5 into main Apr 10, 2026
12 checks passed
@V3RON V3RON deleted the feat/android-ongoing-notifications branch April 10, 2026 11:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant