A web application first.
2.0.4 removes more of the WordPress website feel from the active application, adds browser connectivity awareness and defines how Matrix can become the communication backend without becoming the entire RelayDesk product.
What changed
Astra header/footer/page chrome is hidden on /rd1-app so the application occupies the browser as its own product.
RelayDesk now shows browser connectivity state, disables Sync while offline and refreshes a connected Matrix feed when connectivity returns.
Returning to a visible tab triggers a Matrix refresh only when the prior sync is older than one minute.
Matrix can become the communication transport hub; RelayDesk keeps its own app-backend boundary for identity, connector state, rules and future automation.
Backend decision
External networks -> Matrix bridges -> Matrix homeserver -> Matrix adapter --+
Microsoft / Slack / Email direct adapters ------------------------------+--> RelayDesk Canonical Feed
|
RelayDesk Application Backend -------------------------------------------+--> identity / connector state / priorities / rules / automation
The application backend can later use PostgreSQL/Supabase or another replaceable service. This keeps the communication transport and business/product layer separate.
Still open before production
- Production authentication and protected provider-token handling.
- Live installable PWA service-worker/manifest deployment.
- Real hosted Matrix infrastructure and reviewed bridges for target networks.
- First provider-native direct adapter.
- Persistent application backend for connector/feed metadata and rules.