TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Is realtime functionality of Firebase and Supabase DBs any useful?

4 pointsby harshitjain007over 2 years ago
In my understanding, Firebase Realtime Database can sync the data to the mobile clients only when the app is in foreground and not in killed/background state. This needs developers to handle the killed/background app case separately, and send a push notification to the device (e.g. chat notification). For the right UX, the push notification should only be sent to the apps in killed/background state. So, to detect whether the app is in the foreground or killed/background state, the server will need to maintain a WebSocket connection with every foreground running app. But doesn't this defeat the purpose of using Realtime Database, as the WebSocket itself can be used to sync data now? Or am I missing something?

2 comments

_448over 2 years ago
This may not be what you are looking for, but why not use a combination of Postgres listen&#x2F;notify and PushPin[0] to support push notifications?<p>[0] <a href="https:&#x2F;&#x2F;pushpin.org" rel="nofollow">https:&#x2F;&#x2F;pushpin.org</a>
metadatover 2 years ago
The ~1.2MB per-document limit was a deal killer for my team. Realtime completely irrelevant, we never even got to such a stage.