u/Automatic-Gas-409

You ship a new feature. It passes review. Within hours, you see crashes in production for a specific device/OS combo.

Your options today:

Fix the bug, resubmit, wait 24+ hours for Apple. Users keep crashing.

Push hotfix to Android, hope iOS users don't complain.

Neither feels good.

Sometimes I wonder if there should be a tool that combines feature flags with crash reporting — so when you see a crash spike in your dashboard, you could just turn off the broken feature with one click, no app release needed. Maybe something like this already exists and I haven't found it?

Two questions:

How do you handle this today? Server-side workarounds, kill switches you built yourself, or just live with the App Store delay?

If a one-click solution like that existed, would it actually be useful, or is the problem more nuanced than I'm making it sound?

Genuinely curious how others approach this.

You ship a new feature. It passes review. Within hours, you see crashes in production for a specific device/OS combo.

Your options today:

Fix the bug, resubmit, wait 24+ hours for Apple. Users keep crashing.

Push hotfix to Android, hope iOS users don't complain.

Neither feels good.

Sometimes I wonder if there should be a tool that combines feature flags with crash reporting — so when you see a crash spike in your dashboard, you could just turn off the broken feature with one click, no app release needed. Maybe something like this already exists and I haven't found it?

Two questions:

How do you handle this today? Server-side workarounds, kill switches you built yourself, or just live with the App Store delay?

If a one-click solution like that existed, would it actually be useful, or is the problem more nuanced than I'm making it sound?

Genuinely curious how others approach this.

I’ve always wondered how I can properly view logs and debug issues when I publish an app in release mode.

I recently discovered Firebase Crashlytics, and honestly, it’s impressive. It gives great insights into crashes and helps track real production issues.

But unfortunately, there’s a problem—I’m based in Iran, and Firebase services are restricted here. So I can’t really use it in production.

At first, it felt like a dead end. But instead of giving up, we decided to build own crash analytics system. That’s how Rivium Trace started.

Right now, it's good on solo project and map , but the goal is bigger. Over time, we want to turn it into a stable, production-ready crash reporting and monitoring tool for big compony.

The idea is simple: a lightweight alternative for developers who can’t use tools like Firebase, especially in regions where access is restricted—like Iran, China, and others.

you can see in here : Rivium.co

**Founder here.** I’ve been working on a Backend-as-a-Service platform called Rivium, mainly because I got tired of rebuilding the same backend stack for every side project.

The goal is to simplify the usual setup where you end up combining multiple services just to launch an MVP.

Current modules include:

* Push notifications + in-app messaging * Real-time chat * Authentication (JWT, social login, RBAC) * File storage * Error tracking and logs * Real-time sync * Feature flags * A/B testing

One thing I’m curious about:

For people using Firebase, Supabase, Appwrite, or custom backends:

* What’s the most frustrating part of your current stack? * Do you prefer “all-in-one” platforms or smaller specialized services? * What backend feature do you think most platforms still get wrong?

I’m especially interested in hearing from mobile developers since that’s where most of our focus started.

Not posting this as a sales pitch. Mostly trying to understand whether developers actually want fewer moving parts or if everyone’s already happy duct-taping 11 services together and calling it architecture.

Founder here. I’ve been working on a Backend-as-a-Service platform called Rivium, mainly because I got tired of rebuilding the same backend stack for every side project.

The goal is to simplify the usual setup where you end up combining multiple services just to launch an MVP.

Current modules include:

• Push notifications + in-app messaging
• Real-time chat
• Authentication (JWT, social login, RBAC)
• File storage
• Error tracking and logs
• Real-time sync
• Feature flags
• A/B testing

One thing I’m curious about:

For people using Firebase, Supabase, Appwrite, or custom backends:

• What’s the most frustrating part of your current stack?
• Do you prefer “all-in-one” platforms or smaller specialized services?
• What backend feature do you think most platforms still get wrong?

I’m especially interested in hearing from mobile developers since that’s where most of our focus started.

Not posting this as a sales pitch. Mostly trying to understand whether developers actually want fewer moving parts or if everyone’s already happy duct-taping 11 services together and calling it architecture.