Recus

What is Recus?

Recus is onboarding infrastructure for React Native and Expo apps. It provides a server-driven onboarding flow that can be changed from a dashboard without rebuilding the app or waiting for app-store review.

The Recus SDK includes (1) server-driven UI for defining onboarding screens and fields as JSON, (2) a navigation guard that can enforce mandatory data collection before users can proceed, and (3) field-level analytics and A/B testing for onboarding flows.

Key Features

• Server-driven onboarding schema (JSON): Define screens, fields, validation rules, and field order in Recus and deliver updates on the next app open.
• Instant onboarding changes from a dashboard: Push schema changes live so product teams can update onboarding without opening Jira tickets or requiring an app release cycle.
• Navigation guard with mandatory enforcement: Declare mandatory fields in the schema and use the SDK to prevent navigation into the main app until required data is complete.
• Headless component logic with component registry: Recus controls onboarding logic (which screen/field/variant and what data), while your React Native components handle rendering via a registry (e.g., text/number/toggle/date picker components).
• Field-level analytics: Collect analytics at the field level, including field drop-off and time on field, to identify where users disengage.
• A/B testing for onboarding variants: Run experiments on fields, screens, or flow variants and evaluate results using field-level data.

How to Use Recus

1. Install the React Native SDK (beta access) and wrap your app with the provided provider component (e.g., RecusContextProvider) while registering your input components in a componentRegistry.
2. Configure onboarding from the Recus dashboard by defining screens and fields, specifying types, validation, ordering, and which fields are mandatory.
3. Integrate the navigation guard in your root navigator so the SDK can enforce required fields before users reach the main app.
4. Deploy onboarding updates from the dashboard; Recus pushes the updated onboarding schema so users receive changes on their next app open.

Use Cases

• Product team-led onboarding iteration: Your PM adjusts onboarding order, adds fields, toggles mandatory requirements, or changes validation rules from the dashboard without waiting for a developer sprint and release.
• Mandatory profile completion flows: Require users to complete critical inputs (e.g., full name, email, date of birth) before they can access the main application, enforced by the SDK at the navigation layer.
• Diagnose where onboarding breaks: Use field-level drop-off and time-on-field data to find which specific input (not just the overall screen) causes the biggest drop-offs.
• Test alternative onboarding variants: Run A/B tests on specific onboarding fields, screens, or variants to compare outcomes with causal insight based on field-level data.
• Evolve onboarding without app-store cycles: Change onboarding schema over time (e.g., add a new required or optional field) without submitting an app update for each change.

FAQ

• Is Recus limited to React Native, or does it support Expo too? The site describes Recus as onboarding infrastructure for React Native and Expo apps.

• When do users see onboarding changes? Recus delivers updated onboarding schema so users get changes on their next app open.

• Does Recus require a full app release for every onboarding change? The site states onboarding schema updates can be changed from the Recus dashboard without rebuilds and without app-store waits.

• How does Recus integrate with existing UI components? Recus uses a component registry so your React Native components own rendering, while Recus manages onboarding logic and validation enforcement.

• What analytics does Recus collect for onboarding? Recus collects field-level analytics, including field drop-off and time-on-field, and supports A/B testing on flow variants.

Alternatives

• Build-and-release onboarding with local UI + app-store updates: Traditional approach where onboarding changes require code changes and a new release, often involving app review and longer turnaround.
• Client-side form engines with custom navigation logic: Form-focused solutions can manage validation and input UX, but the source contrasts Recus with tools that provide form engines without the onboarding dashboard control and navigation guard behavior.
• Gradual feature rollout tools (e.g., remote flags) combined with custom onboarding code: Remote configuration can change client behavior, but you still need to implement onboarding logic, navigation enforcement, and analytics yourself.
• Static onboarding content/tour tools: Content or tour tools can guide users with tooltips or tours, but they don’t replace schema-driven onboarding, mandatory enforcement, or the field-level analytics described for Recus.