riuve

Most apps treat notifications as an afterthought. That's why open rates are 2%. Riuve treats them as infrastructure: • Timezone-aware quiet hours • Frequency caps + per-user daily limits • Offline queue that never drops an event Because engagement starts with respect. #buildinpublic #ReactNative #nextjs #devtools #flutter #expo #exposdk #saas

Getting Expo + Firebase push to cooperate is a rite of passage, respect 🙏 For the event pagination part — if you're ever tired of hand-rolling the analytics side too, Riuve handles batching, offline queue and pagination out of the box (Expo-native SDK). No pressure, just sharing in case it saves you another 4h night. And more: riuve.com

He dormido 4h pero merece la pena. Conseguí que me funcionara las notificaciones push de Expo con Firebase en mi app. Ahora me pondré a corregir ciertos problemas de rendimientos añadiendo paginación en los eventos.

Yep, one config. We use Expo Server SDK under the hood, so the push token from expo-notifications works for both iOS and Android — no separate APNs/FCM setup on your end. If you're already mid-project, migration is usually a 10-min job. Shoot us a DM — happy to set you up with a free Growth plan as a thank-you for being an early user.

@useriuve good timing — mid React Native + Expo project and notification setup is always the annoying part. does Riuve handle push for both iOS and Android from one config, or still separate setups?

Building a notification stack used to be a project. Now it’s one line of code. Riuve: event tracking, push, email, and drip automation — all behind a single SDK. Built for Expo and Next.js. #buildinpublic #ReactNative #nextjs #devtools #expo #sdk

Riuve now has an MCP server. Your AI editor can query your analytics directly. No dashboard, no tab switching. "What happened yesterday?" → answered. "Top events this week?" → answered. "Retention by cohort?" → answered. 16 tools, one token. Works with Claude, Cursor, Windsurf, Zed, and Codex. Setup: one command. Time: 2 minutes. Details here ↓ riuve.com/en/blog/introd…

Riuve now supports Flutter. Natively. Not a wrapper around a web SDK. Not a community fork. A from-scratch implementation with full feature parity. Offline queue, intelligent batching, session management, FCM token sync — everything our React Native SDK does, now in Dart. Riuve.track() before init? Queued. App goes offline mid-batch? Persisted. Network comes back? Auto-flushed. One singleton. Three lines to set up. Zero events lost. Read the full setup guide ↓ riuve.com/en/blog/flutte…

Your user is on the subway, in a tunnel, on a plane. They opened your app, did something. But there's no internet — and in most systems, those events are just gone. In Riuve, events are written to the device first. When the connection comes back, they're sent automatically. Details here ↓ riuve.com/en/blog/offlin…

Bildirim göndermek kolay görünür. Ama iş büyüyünce tablo değişiyor. Push için bir araç, email için başkası, otomasyon için üçüncüsü. Bunları birbirine bağlamak asıl işin kendisi oluyor. Riuve, bu karmaşayı bitiriyor. Kullanıcıyı izliyorsun, segmente ediyorsun, otomasyonu kuruyorsun ve gönderiyorsun — geri kalanını Riuve hallediyor. Tüm hikayeyi anlattım ↓ riuve.com/en/blog/events…

Every push notification tool's onboarding starts the same way: "First, install our SDK." Then 3 hours later you're debugging native build errors, you have two sources of truth for user events, and somebody on the team is asking which dashboard to trust. We built Riuve with a different assumption: you're already tracking events somewhere. Why do it twice? Paste your Mixpanel API secret or PostHog personal API key into Riuve. Every 5 minutes, we pull your events — PostHog also gives us user profiles and up to a year of historical backfill. Everything is deduped, mapped to sessions, and immediately usable in campaign segments. The event a user fired in Mixpanel yesterday can trigger a push notification today. No SDK install. No re-instrumentation. No touching your mobile build. Your analytics stack stays where it is. Your marketing stack finally gets an engine behind it. #buildinginpublic #productanalytics #growthmarketing #mixpanel #posthog

Most analytics SDKs do this: Call track() before init() → event lost. Fire an event in airplane mode → event lost. Network drops mid-batch → event lost. There's no such thing as "mostly delivered." Either it ships, or it doesn't. We fixed all three in Riuve — because a customer's cart abandonment event shouldn't "usually" arrive. The result: events fired before init() are queued with their original timestamps, offline events persist to storage, and failed batches replay on the next cold start. Before your next integration, ask: when does this SDK drop my events? If you don't know the answer — it probably already has. #buildinginpublic #distributedsystems #mobiledevelopment #productanalytics

Every notification follows a pipeline. Target evaluation → quiet hours check → rate limits → A/B variant selection → delivery — all in under 12ms. We wrote a deep dive into how Riuve's campaign delivery system works, minute by minute: → How target rules are evaluated at scale → Quiet hours and timezone-aware delivery → A/B testing with deterministic variant assignment → Rate limiting and delivery guarantees Push, email, or in-app — same pipeline, same reliability. Read the full breakdown: riuve.com/blog/campaign-… #notifications #engineering #saas