WE ARE HIRING • WE ARE HIRING • 
Certified Flutter Consultants|RevenueCat Technical Partners|4.9★ Rated on Clutch|Top Rated Plus · Upwork|250+ Projects Delivered|200+ Happy Clients Worldwide|Delivering Excellence Since 2019|The Expertise Behind Every Product We Build|Helping Businesses Across Industries Innovate|Voices of the Companies We’ve Helped|
Certified Flutter Consultants|RevenueCat Technical Partners|4.9★ Rated on Clutch|Top Rated Plus · Upwork|250+ Projects Delivered|200+ Happy Clients Worldwide|Delivering Excellence Since 2019|The Expertise Behind Every Product We Build|Helping Businesses Across Industries Innovate|Voices of the Companies We’ve Helped|
Home/Blogs/Rating and Feedback Collector
flutterJuly 23, 2024

Rating and Feedback Collector

Introduction User feedback collection cannot be overemphasized, therefore, if an app is to grow in both quality and satisfaction, The package offers a developer versatile solutions into making bars rated with icons, emoj

Jay Leshwala

Flutter

Rating and Feedback Collector

Introduction

User feedback collection cannot be overemphasized, therefore, if an app is to grow in both quality and satisfaction, The package offers a developer versatile solutions into making bars rated with icons, emojis, and even custom images. Further, this allows dynamic feedback alerts, hence allowing the user to include as much detail in their feedback as possible and rate your app. This will walk you through the setup and usage of this package, hence you can make full use of its features.

Key Features

  • Custom Icon Rating: Use any icon to represent rating units.
  • Smiley Emojis Rating: Default emoji images to express ratings.
  • Custom Image Rating: Use your custom images for ratings.
  • Feedback Alert Box for Low Ratings: Prompt users to provide feedback if they rate low.
  • Redirect to Store for High Ratings: Redirect users to the app store for a review if they rate high.
  • Customizable UI & Contents: Fully customizable to fit your app’s theme.
  • Submission Callback: Get feedback data with a callback function.

Installation

First, add the rating_and_feedback_collector package to your pubspec.yaml file:

dependencies:
rating_and_feedback_collector: ^0.0.2

Then, run pub get to fetch the package.
Importing the Package
Next, import the package into your Dart file:

import 'package:rating_and_feedback_collector/rating_and_feedback_collector.dart';

Usage

Here are examples of how to use the package’s main features:

Rating Bar with Icons

The RatingBar widget allows you to use icons to represent ratings. You can customize the icons, their size, colors, and whether half ratings are allowed.

double _rating = 0.0;
RatingBar(
iconSize: 40, // Size of the rating icons
allowHalfRating: true, // Allows selection of half ratings
filledIcon: Icons.star, // Icon for a filled rating unit
halfFilledIcon: Icons.star_half, // Icon for a half-filled rating unit
emptyIcon: Icons.star_border, // Icon for an empty rating unit
filledColor: Colors.amber, // Color of filled rating units
emptyColor: Colors.grey, // Color of empty rating units
currentRating: _rating, // Set initial rating value
onRatingChanged: (rating) { // Callback triggered when the rating is changed
setState(() { _rating = rating; });
},
),

Rating Bar with Emoji Images

The RatingBarEmoji widget uses default emoji images to represent ratings.

double _rating = 0.0;
RatingBarEmoji(
imageSize: 45, // Size of image in the rating bar
currentRating: _rating, // Set initial rating value
onRatingChanged: (rating) { // Callback triggered when the rating is changed
setState(() { _rating = rating; });
},
),

Rating Bar with Custom Images

The RatingBarCustomImage widget allows you to use custom images for different rating levels.

double _rating = 0.0;
RatingBarCustomImage(
imageSize: 45, // Size of image in the rating bar
currentRating: _rating, // Set initial rating value
activeImages: const [
AssetImage('assets/Images/ic_angry.png'),
AssetImage('assets/Images/ic_sad.png'),
AssetImage('assets/Images/ic_neutral.png'),
AssetImage('assets/Images/ic_happy.png'),
AssetImage('assets/Images/ic_excellent.png'),
],
deActiveImages: const [
AssetImage('assets/Images/ic_angryDisable.png'),
AssetImage('assets/Images/ic_sadDisable.png'),
AssetImage('assets/Images/ic_neutralDisable.png'),
AssetImage('assets/Images/ic_happyDisable.png'),
AssetImage('assets/Images/ic_excellentDisable.png'),
],
onRatingChanged: (rating) { // Callback triggered when the rating is changed
setState(() { _rating = rating; });
},
),

Customization Properties

The package offers various properties to customize the rating bar and feedback dialog:

  • currentRating (double): Set initial rating value
  • filledIcon (only for RatingBar) (IconData?): Icon for a filled rating unit
  • halfFilledIcon (only for RatingBar) (IconData?): Icon for a half-filled rating unit
  • emptyIcon (only for RatingBar) (IconData?): Icon for an empty rating unit
  • filledColor (only for RatingBar) (Color?): Color of filled rating units
  • emptyColor (only for RatingBar) (Color?): Color of empty rating units
  • iconSize (double?): Size of the rating icons
  • onRatingChanged (Function(double)): Callback triggered when the rating is changed
  • allowHalfRating (only for RatingBar) (bool?): Allows selection of half ratings
  • isGoogleFont (bool?): Set to true for using Google fonts
  • fontFamilyName (String?): Custom font family name or Google font family name
  • showFeedbackForRatingsLessThan (double?): Threshold rating value below which feedback box is shown
  • feedbackBoxTitle (String?): Title for the feedback box
  • lowRatingFeedbackTitle (String?): Title for feedback options in the low rating feedback box
  • lowRatingFeedback (List?): List of feedback strings for low ratings
  • showDescriptionInput (bool?): Option to show input box for user descriptions in the feedback dialog
  • descriptionTitle (String?): Title for the description input box in the feedback dialog
  • descriptionPlaceHolder (String?): Placeholder text for the description input box
  • descriptionCharacterLimit (int?): Character limit for the description input
  • submitButtonTitle (String?): Title for the submit button in the feedback dialog
  • onSubmitTap (Function(selectedFeedback, description)): Callback function triggered on submission of feedback
  • showRedirectToStoreForRatingsGreaterThan (double?): Threshold rating value above which the app redirects to the store for a review
  • androidPackageName (String?): Android package name for the app, used in the store redirect
  • iosBundleId (String?): iOS bundle ID for the app, used in the store redirect
  • innerWidgetsBorderRadius (double?): Border radius for the feedback dialog widgets
  • alertDialogBorderRadius (double?): Border radius for the feedback dialog

Conclusion

Rating_and_feedback_collector Package is the optimal solution for adding highly flexible rating bars and in-app feedback alerts into your Flutter app.
By incorporating this package you can raise user’s interest, collect useful feedback and eventually boost your app’s ratings in the store. Include this package into your app and enjoy its flexible and user-friendly elements.

Keep Reading
Related Articles

You Might Also Like

FlutterFlow’s New Feature: App Events (A Game Changer for Scalable Apps)
flutterApr 21, 2026

FlutterFlow’s New Feature: App Events (A Game Changer for Scalable Apps)

Building scalable applications in low-code platforms has always been a balance between speed and maintainability. While FlutterFlow makes UI development incredibly fast, managing communication between different parts of an app could sometimes become complex. But with the introduction of App Events, FlutterFlow has taken a major step forward — bringing cleaner architecture, better performance, and a much more scalable approach to app development. The Problem Before App Events Before this update, handling communication between screens or components often involved: Passing multiple navigation parameters Managing complex global or local state Writing tightly coupled logic between screens As apps grew larger, this approach became: Hard to maintain Difficult to debug Less scalable What Are App Events? App Events introduce a decoupled communication system inside FlutterFlow. Core Idea: Trigger an event from anywhere in the app Listen and respond to that event from anywhere No direct connection between components is required. This means your app becomes: More modular Easier to maintain Much cleaner in terms of logic How It Works (Simple Example) Let’s say a user adds an item to the cart 🛒 Without App Events: Manually update cart badge Refresh product list Update summary screen Pass state across multiple screens With App Events: Trigger event → “Cart Updated” All relevant UI components automatically react That’s it. No messy logic. Key Highlights Global Events App-level events Handled across the entire application Processed sequentially Perfect for: Authentication state changes Analytics tracking Logging Local Events Scoped to specific pages or components Support multiple listeners Trigger instant UI updates Perfect for: UI refresh Component communication Dynamic interactions Why This Feature Matters App Events bring FlutterFlow closer to modern software architecture patterns, such as: Event-driven systems Loose coupling Reactive UI updates Benefits: Less complex code structure Better performance Easier debugging Improved scalability My Take This is easily one of the most impactful updates in FlutterFlow in recent times. It solves a real problem developers face when scaling apps and introduces a pattern that aligns with how modern applications are built. Final Thoughts FlutterFlow continues to evolve beyond just a UI builder — it’s becoming a serious development platform capable of handling complex applications. App Events are a big step in that direction. If you haven’t explored it yet, now is the time. #FlutterFlow #NoCode #LowCode #AppDevelopment #MobileDevelopment #Firebase #UIUX #TechUpdate #Developers

Read more
Integrating Tamara Payment Gateway in a FlutterFlow Application
flutterApr 21, 2026

Integrating Tamara Payment Gateway in a FlutterFlow Application

In today’s digital ecosystem, integrating a reliable payment gateway is essential for delivering a smooth and secure user experience. However, building a payment system isn’t just about processing transactions — it’s about ensuring security, reliability, and compliance, all while maintaining a seamless user journey. Recently, I worked on integrating the Tamara Payment Gateway into a FlutterFlow application, creating a complete end-to-end payment workflow — from initiating transactions to handling real-time updates. The Goal The objective was to implement a secure and scalable payment flow that: Enables users to complete payments smoothly Handles transaction states reliably Ensures compliance with Tamara’s payment standards Works seamlessly across development and production environments The Implementation The integration involved connecting Tamara’s APIs with the FlutterFlow application and managing the full payment lifecycle. Key Features Implemented Tamara Checkout API Integration We used Tamara’s Checkout API to: Initiate payment sessions Redirect users to the hosted checkout page Process transactions securely Secure Payment Handling Security was a top priority. The implementation ensured: Proper API request validation Safe handling of transaction data Compliance with Tamara’s payment flow Webhook Integration for Real-Time Updates To keep track of payment status: Implemented webhooks to receive real-time updates Handled events such as: Payment success Payment failure Transaction updates This ensures the app always reflects the correct payment status. Payment Method Support Enabled support for: Visa cards Mada cards This ensures compatibility with regional payment preferences. Environment Configuration Set up both environments: Sandbox (Development) for testing Production for live transactions This separation ensures safe development and smooth deployment. Reliable Request & Response Handling Carefully managed API communication to: Handle success and failure cases Prevent duplicate transactions Ensure consistency across the payment flow Key Challenge: Hosted Checkout Limitations One of the most interesting aspects of this integration was understanding the limitations of Tamara’s hosted checkout flow. Unlike custom UI payment solutions: The payment interface is controlled by Tamara UI customization options are limited Why This Matters At first, this might seem like a limitation, but it actually ensures: Higher security standards Compliance with payment regulations Reduced risk of implementation errors Understanding these constraints helped align the integration with best practices recommended by Tamara. Final Result The final implementation delivered: A stable and secure payment experience Smooth transaction processing Accurate real-time payment updates Full compliance with Tamara’s standards Users can now complete payments confidently, knowing the system is both secure and reliable. Key Learnings Balancing UX and Security Not all payment flows allow full UI control. Sometimes, prioritizing security and compliance is more important than customization. Importance of Webhooks Webhooks are critical for: Real-time updates Backend synchronization Reliable transaction tracking Tech Stack FlutterFlow Dart Tamara Payment Gateway APIs Webhooks for real-time updates Final Thoughts This integration reinforced an important lesson: A great payment system is not just about UX — it’s about trust, security, and reliability. By combining FlutterFlow with Tamara’s infrastructure, we were able to build a solution that meets both user expectations and industry standards. If you’re working on payment integrations, always remember: Understand platform limitations Follow recommended flows Prioritize security over customization #FlutterFlow #PaymentGateway #Tamara #Fintech #MobileDevelopment #APIIntegration #Webhooks

Read more
1. How I Built a Production-Ready AI Chat App in FlutterFlow (With OpenAI + Firebase)
flutterApr 20, 2026

1. How I Built a Production-Ready AI Chat App in FlutterFlow (With OpenAI + Firebase)

Introduction AI is everywhere in 2026 — but building a production-ready AI chat app is still challenging, especially when using low-code tools like FlutterFlow. In this article, I’ll walk you through how I built a scalable AI chat system using FlutterFlow + Firebase + OpenAI API. Architecture Overview My setup looks like this: Frontend → FlutterFlow UI Backend → Firebase (Firestore + Cloud Functions) AI Engine → OpenAI API Storage → Chat history in Firestore Chat Data Structure Each message is stored like this: { "userId": "123", "message": "Hello AI", "response": "Hi, how can I help?", "timestamp": "server_time" } This allows: Easy chat history retrieval Real-time UI updates Scalable structure Securing OpenAI API Never expose your API key in the frontend. Instead: Use Firebase Cloud Functions Send request → backend → OpenAI → return response This keeps your app secure. Handling Token Usage (Cost Control) AI APIs can get expensive. What I did: Limit message length Store token usage Restrict free users (daily limit) UI Challenges & Solutions Problem: Chat UI lag with many messages Solution: Pagination Lazy loading Efficient Firestore queries Final Result Real-time AI chat Scalable backend Controlled cost Smooth UI Final Thoughts FlutterFlow is powerful — but combining it with backend logic is the real game-changer.

Read more
FlutterFlow + RevenueCat: Complete Guide to Subscription Apps
flutterApr 15, 2026

FlutterFlow + RevenueCat: Complete Guide to Subscription Apps

Introduction If you’re building a SaaS or premium mobile app, subscriptions are one of the most reliable monetization models. But implementing subscriptions correctly is not just about adding a payment button — it involves: Secure validation Real-time status updates Handling edge cases (expiry, restore, refunds) In this guide, I’ll walk you through how I implemented a production-ready subscription system using FlutterFlow + RevenueCat + Firebase. Why RevenueCat? Instead of directly handling App Store / Play Store billing, I used RevenueCat because it simplifies everything. Key Benefits: Single integration for both iOS & Android Handles receipts, validation, and renewals Real-time subscription status via webhooks Reduces development complexity Without RevenueCat, managing subscriptions manually becomes very complex. System Architecture (Simple View) Here’s how the system works: FlutterFlow App (Frontend) User interacts with UI (Upgrade, Restore) RevenueCat SDK Handles purchase flow RevenueCat Server Validates transactions Firebase (Firestore + Cloud Functions) Stores subscription status & triggers updates Complete Subscription Flow Here’s the exact flow I implemented: 1. User Action User clicks “Upgrade to Premium” 2. Purchase Trigger RevenueCat SDK opens native purchase screen (App Store / Play Store) 3. Payment Processing Payment handled securely by Apple/Google RevenueCat validates purchase 4. Webhook Trigger RevenueCat sends event → Firebase Cloud Function 5. Firestore Update User document is updated: { "isPremium": true, "plan": "monthly", "expiryDate": "timestamp" } 6. UI Update FlutterFlow listens to Firestore Premium features unlock instantly Firestore Database Structure To keep things scalable and clean, I used this structure: users collection { "userId": "123", "isPremium": true, "plan": "yearly", "expiryDate": "timestamp" } subscriptions collection { "planId": "monthly_001", "price": 9.99, "duration": "1 month" } events collection (VERY IMPORTANT) { "userId": "123", "eventType": "PURCHASE", "timestamp": "server_time" } This helps in: Tracking revenue Debugging issues Analytics Handling Edge Cases (Most Developers Miss This) This is where most apps fail 1. Expired Subscription Check expiryDate regularly Disable premium access automatically 2. Restore Purchases Add Restore button Sync with RevenueCat Update Firestore again 3. Cancelled Subscription User cancels from App Store RevenueCat webhook updates backend Access removed after expiry 4. Refunds RevenueCat sends refund event Immediately update user access Backend Validation (CRITICAL) Never trust frontend logic Always validate subscription from backend using: Why? Prevents fake unlock hacks Ensures real subscription status Keeps your app secure Performance & Cost Optimization Here’s what I optimized: Avoid Excessive Reads Store only required subscription fields Don’t fetch full history every time Use Real-Time Listeners Smartly Listen only to user document Avoid unnecessary listeners Cache Subscription Status Reduce repeated API calls UI Best Practices (Conversion Focused) Subscription UI is not just design — it impacts revenue 💰 What worked for me: Highlight best plan (yearly) Show discount badge (Save 30%) Clear CTA: “Upgrade Now” Add trust elements (secure payment, cancel anytime) Final Result After implementing this system: Smooth and secure purchase flow Real-time subscription updates Scalable backend architecture Reduced bugs and edge case failures Final Thoughts FlutterFlow + RevenueCat is a powerful combination for building subscription-based apps quickly. But the real difference comes from: Proper backend validation Clean database design Handling real-world edge cases That’s what turns a basic app into a production-ready SaaS product.

Read more