The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Serviwise (Emergency Service Platform)
Serviwise is a real-time emergency service platform developed with Flutter that connects users with nearby service providers for instant roadside assistance. The app supports services such as bike repair, fuel delivery, and car mechanic support with live tracking, in-app chat, push notifications, and secure authentication. It features Google Maps integration, Firebase real-time database operations, provider management, ratings & reviews, and seamless user-provider communication for a complete on-demand service experience.
Key Features:
• Firebase Phone Authentication for secure user login
• Service provider registration and verification system
• Real-time service request and acceptance workflow
• Live location tracking using Google Maps API
• In-app chat system for user-provider communication
• Multi-category services (Bike, Car, Fuel Delivery)
• Rating and review system for service providers
• Push notifications for new requests and updates
• Service history and tracking
• Real-time database with Firestore for instant updates Secure payment integration for service payments
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Cancelling a purchase and failing a purchase reach your Flutter code the same way, as a PlatformException. That is how a paywall ends up showing a red error to someone who simply changed their mind on the store sheet.
PurchasesErrorHelper.getErrorCode is what distinguishes them, and two outcomes are not enough. A single call to Purchases.purchase can end five ways: cancelled, pending, completed, failed and unresolved. Pending is the one that catches people out. A parent still has to approve the purchase, or a slow payment method has to settle, and RevenueCat grants no entitlement until the store confirms it.
Which means the paywall screen should not be what decides access. A pending purchase can complete after the paywall closes or after the app has been killed, and RevenueCat does not push that change to the device. Keep a CustomerInfo listener in an object that lives as long as the app, and have every paid feature read the entitlement from it rather than from whatever the purchase call returned.
https://www.duskolicanin.com/blog/flutter-subscription-pending-cancelled-purchase
duskolicanin.com
Handle Pending and Cancelled Flutter Purchases
Handle RevenueCat cancelled and pending purchases in Flutter: map error codes to paywall states and unlock only from an active entitlement listener.
This is such a real pain point! So many paywalls break exactly here - treating a user cancellation as a crash. Thanks for pointing out PurchasesErrorHelper.getErrorCode to distinguish it. Handling cancelled vs pending correctly is crucial for UX, no one wants a red error for changing their mind. Saving this!
Such a sleek and professional aesthetic.
AI CRM App Design and Development...
From intuitive UI/UX to intelligent workflows, AI-powered CRM
applications that simplify operations, automate tasks, and turn data into actionable insights.
