1244 results found

1. Allow Firebase project root to be configured independently of firebase.json location

   The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.

   While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.

   This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.

   It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.

   Example

   Consider an Nx monorepo structured like this:

   repo/
   ├── apps/
   ├── libs/
   ├── dist/
   │ └── apps/
   │ └── web/
   ├── infrastructure/
   │ └── firebase/
   │ ├── firebase.json
   │ ├── firestore.rules
   │ ├── firestore.indexes.json
   │ └── storage.rules
   ├── nx.json
   └── package.json

   From an organizational standpoint, keeping Firebase-specific infrastructure under:

   infrastructure/firebase/

   is desirable.

   The CLI supports selecting that file:

   firebase deploy --config infrastructure/firebase/firebase.json

   However, if the Hosting configuration contains:

   {
   "hosting": {
   "public": "dist/apps/web"
   }
   }

   the path is effectively resolved relative to:

   infrastructure/firebase/

   rather than the actual workspace root.

   The build output produced by Nx is located at:

   repo/dist/apps/web

   so moving "firebase.json" also unintentionally changes the filesystem context of the Firebase project.

   Current workaround

   The practical workaround is to leave "firebase.json" at the workspace root:

   repo/
   ├── firebase.json
   ├── apps/
   ├── libs/
   ├── dist/
   └── infrastructure/
   └── firebase/
   ├── firestore.rules
   ├── firestore.indexes.json
   └── storage.rules

   and then reference Firebase-specific files from the root configuration.

   This works, but it means "firebase.json" becomes a special root-level file purely because its location controls the CLI's filesystem context.

   In larger monorepos, that makes Firebase configuration harder to organize consistently with other infrastructure.

   Proposed behavior

   It would be useful to provide a way to explicitly specify the Firebase project root separately from the config file.

   For example, a CLI option:

   firebase deploy \
   --config infrastructure/firebase/firebase.json \
   --project-root .

   or perhaps a configuration property:

   {
   "root": "../../",
   "hosting": {
   "public": "dist/apps/web"
   }
   }

   The exact API is less important than allowing these two concepts to be independent:

   1. Location of "firebase.json"
   2. Root directory used for resolving project-relative paths

   Why this matters

   This becomes particularly useful in monorepos using tools such as Nx, where:

   • application source lives under "apps/"
   • shared code lives under "libs/" or "packages/"
   • build artifacts are emitted to a workspace-level "dist/"
   • deployment/infrastructure configuration may live under "infrastructure/"

   In that structure, the location of a Firebase configuration file is an organizational concern and doesn't necessarily represent the root of the application workspace.

   Separating the config location from the project root would make Firebase CLI behavior more flexible without changing the existing default behavior.

   Backwards compatibility

   Existing behavior could remain unchanged when no explicit project root is supplied.

   For example:

   firebase deploy

   would continue using the directory containing "firebase.json" as it does today.

   Only users who explicitly provide a root would get the new behavior.

   Additional context

   I initially expected "--config" to control only which Firebase configuration file was loaded.

   The surprising part was discovering that relocating the configuration also effectively relocates the filesystem context used by Firebase.

   A separate root option would make "--config" much more useful for monorepo and infrastructure-oriented repository layouts.

   The Firebase CLI currently appears to treat the directory containing "firebase.json" as the effective root directory for the Firebase project.

   While "--config" allows "firebase.json" itself to be moved, moving the config file also changes how relative paths inside that configuration are resolved.

   This creates an awkward limitation for monorepos, where configuration files may naturally live in an infrastructure/configuration directory while build artifacts remain at the workspace root.

   It would be useful if the Firebase CLI allowed the configuration file location and the project root to be specified independently.

   Example

   Consider an Nx monorepo structured like this:

   repo/
   ├── apps/
   ├──… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase CLI  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release

   Production Multi-Provider Integration Scheme For production readiness, for the Google IO 2027 release a service that after staring into your devices camera for 20 seconds will log you into any account email platform or social media that's ever log your face and stored it in the cloud

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Authentication  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Good App put on teachers and the liners

   This app is very very intelligent is good from teachers underlying all the student the healthy us from exam or question you can solve it

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Propagate Original Client IP through Firebase Console Proxy for VPC-SC Enforcement

   We are encountering a block when placing our project under VPC Service Controls enforcement. When a user attempts to access the Storage tab in the Firebase Console, it fails with an "Unknown Error" (Audit logs show NOMATCHINGACCESS_LEVEL with an empty clientIp). The Firebase Console currently acts as an internal proxy, routing traffic through Google's internal infrastructure. Because it traverses these internal paths, the end-user's local corporate egress IP is entirely stripped before the API payload reaches the protected Storage endpoint (storage.googleapis.com). We have strict compliance requirements to restrict access solely to trusted corporate network IPs, meaning the standard VPC-SC workaround of allowing all sources (accessLevel: "*") is not an option for us. We request that the Firebase Console backend be configured to extract and propagate the end-user's context. Specifically, the One Platform service configuration should be updated to request google.rpc.context.OriginContext in the context.rules section of the service YAML. This will allow the original client IP to pass through the GFE/proxy so that VPC-SC can accurately evaluate the IP against our perimeter policies.

   We are encountering a block when placing our project under VPC Service Controls enforcement. When a user attempts to access the Storage tab in the Firebase Console, it fails with an "Unknown Error" (Audit logs show NOMATCHINGACCESS_LEVEL with an empty clientIp). The Firebase Console currently acts as an internal proxy, routing traffic through Google's internal infrastructure. Because it traverses these internal paths, the end-user's local corporate egress IP is entirely stripped before the API payload reaches the protected Storage endpoint (storage.googleapis.com). We have strict compliance requirements to restrict access solely to trusted corporate network IPs, meaning the standard… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Storage for Firebase  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Table Event Triggers

   In additional to the onMutationExecuted, we would love to have events on table mutations.

   • onRowUpdated
   • onRowCreated
   • onRowDeleted

   onMutationExecuted is already launched in Nov 2026. https://firebase.blog/posts/2025/11/dataconnect-nov25

   12 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SQL Connect (Data Connect)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Provide Native Document Counters and Metadata for Firestore Collections

   Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read costs on large production databases.

   Problem:Currently, finding the total number of documents inside a Firestore collection requires building custom client-side listeners or cloud functions to maintain manual counter fields. This adds boilerplate code, introduces latency, and risks running into write rate limitations unless complex distributed counters are built.Proposed Solution:Firebase should provide an out-of-the-box, native SDK method (e.g., a simple client-side function) that securely requests the exact document count from the server's index layer without needing to download, fetch, or bill for individual document data payloads.Why this matters:This feature is critical for building cheap, efficient pagination UI, analytics dashboards, and status trackers without incurring massive read… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firestore  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. car racing game

   Online Gaming Platform – Project Requirements Document

   1. Platform Name

   ---

   2. Project Objective

   The platform will provide a secure online gaming experience where users can create accounts, verify their identity, manage a digital wallet, and participate in games. The system will include secure payment processing, user verification, and fair gameplay mechanisms.

   3. User Registration

   • Full Name
   • Mobile Number
   • Email Address
   • Password
   • OTP Verification
   • Age Verification (where legally required)

   4. Identity Verification (KYC)

   • Government ID Upload
   • Selfie Verification
   • Mobile Number Verification
   • Email Verification
   • KYC Approval Status

   5. Digital Wallet System

   The platform will include a secure wallet that allows users to:

   • View Balance
   • View Transaction History
   • Deposit Funds
   • Withdraw Funds
   • Monitor Account Activity

   6. Payment System

   Supported payment methods may include:

   • Digital Banks
   • Mobile Wallets
   • Bank Transfers
   • Debit/Credit Cards

   All payment transactions will be processed through secure, encrypted channels.

   7. Gaming Features

   • Multiplayer Game Modes
   • Leaderboards
   • Ranking System
   • Match History
   • Fair Play System
   • Anti-Cheat Protection

   8. User Dashboard

   • User Profile
   • Wallet Balance
   • Game History
   • Achievements
   • Notifications
   • Account Settings

   9. Admin Panel

   • User Management
   • KYC Approval Management
   • Transaction Monitoring
   • Reports and Analytics
   • Security Monitoring
   • Customer Support Tools

   10. Security Features

   • Two-Factor Authentication (2FA)
   • Data Encryption
   • Secure Login System
   • Fraud Detection
   • Suspicious Activity Monitoring

   11. Legal & Compliance Requirements

   • Compliance with Local Laws
   • Privacy Policy
   • Terms and Conditions
   • Age Verification Requirements
   • Financial Compliance Standards

   12. Future Enhancements

   • Android Application
   • iOS Application
   • Live Chat Support
   • Referral Program
   • Tournament System
   • Multi-Language Support
   • AI-Based Security Monitoring

   Project Summary

   This project aims to build a modern, secure, and scalable online gaming platform with user registration, identity verification, digital wallet management, secure payment integration, fair gameplay systems, and a professional administration panel.

   Online Gaming Platform – Project Requirements Document

   1. Platform Name

   ---

   2. Project Objective

   The platform will provide a secure online gaming experience where users can create accounts, verify their identity, manage a digital wallet, and participate in games. The system will include secure payment processing, user verification, and fair gameplay mechanisms.

   3. User Registration

   • Full Name
   • Mobile Number
   • Email Address
   • Password
   • OTP Verification
   • Age Verification (where legally required)

   4. Identity Verification (KYC)

   • Government ID Upload
   • Selfie Verification
   • Mobile Number Verification
   • Email Verification
   • KYC Approval Status

   5. Digital Wallet System

   The platform will include a secure wallet that allows users to:

   • … more
   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Firebase Studio  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. App Distribution should have at least basic management of email notifications

   There is no option to set email preferences for tester groups in Firebase App Distribution. It is unnecessary to pester everyone with emails when they can find the last app version in App Tester.

   60 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   10 comments  ·  App Distribution  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Cancel Extensions Deprecation

   Continue offering the Extensions service, do not shut it down.

   Extensions are a core feature of Firebase, and the work required for customers to replace them is unacceptable.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Extensions  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Improve SEO Support for Content-Driven Websites

    I suggest that Firebase improve its support for content-driven websites by adding better SEO tools, enhanced static site optimization, and easier integration with search engines.

    I manage a gaming website called TomodachiLifeROM, where I publish game guides, tutorials, and gaming resources. Features such as built-in sitemap generation, improved metadata management, better structured data support, and more detailed performance recommendations would make Firebase Hosting even more useful for publishers.

    https://support.google.com/sites/thread/451587408?hl=en&sjid=16379941293809233418-EU

    It would also be helpful to have clearer documentation and examples for deploying SEO-friendly websites while maintaining excellent performance.

    Thank you for considering this suggestion.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Hosting  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. firebase init hosting:github environment secret

    The firebase init hosting:github command should support creating secrets for a GitHub environment for better security posture.

    https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets#creating-secrets-for-an-environment

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase CLI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. More information in errors for native sql statements

    Errors in native sql statements like in _execute always result in the same "Invalid SQL statement" error without any further information, which makes it really difficult to debug. More data - for example the part of the SQL statement that is invalid - would be really helpful! Especially as this error also seems to be thrown when the SQL is perfectly fine but a wrong _execute syntax is used, which should not throw an "Invalid SQL statement" error, as it is not about SQL!

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  SQL Connect (Data Connect)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. usage is not acurate,

    just shows totals and i cannot see exactly at what time a read of documents was made, starting a scalable app is very frustrating when I can see 1K reads when my app it was even open, from where?, i just have one app and is in my phone, when I se monitoring I just can see group data, even worse the date is pacific time, even more confusing although I know to convert the timeline, I don't think is hard to show the local time right?

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firestore  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. publish a GCP / firebase documentation MCP server

    Enable fetch and query tools in an MCP server for the whole GCP, or the firebase documentation.

    12 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Agent Skills & MCP Server  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. We should be able to add more then 5 goals in a AB Test. Thats crucial for optimizers, i am sure you miss lots of customers because of it.
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Test Lab  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Provide an Nx plugin or support the community one

    There's a plugin, but it doesn't receive much love. The main problem is effort - Nx keeps doing breaking changes and the plugin gets broken with pretty much every new Nx version. Not even to mention that they dropped the e2e part for functions.

    Would be great if the Firebase Team could work on it:

    https://github.com/simondotm/nx-firebase

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Fr Tournaments

    Nuralom

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Cloud Functions for Firebase  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Keep Firebase Studio alive until Google offers a real replacement

    Firebase Studio is being shut down without a true replacement, and that is a serious mistake.

    For many of us, Firebase Studio was not just an experiment — it was a practical, browser-based development workspace deeply integrated with Firebase, accessible from anywhere, and useful for real production workflows.

    The alternatives being pointed to are not equivalent:

    Google AI Studio is more of an AI playground than a full development environment.
    Antigravity appears to require high-end local hardware, which defeats the purpose of a cloud-based workspace you can use from any machine.
    Firebase Studio gave developers something extremely valuable: flexibility, accessibility, low hardware dependency, and direct connection to Firebase projects. Removing it without feature parity is not a migration — it’s a downgrade.

    We ask Google to:

    delay the shutdown of Firebase Studio until there is a true replacement;
    publish a clear roadmap for feature parity;
    clarify what will happen to users who paid for extra workspaces;
    listen to the community before removing a tool that many developers genuinely rely on.
    If Firebase Studio has been part of your workflow, please sign and help show Google that this product should not disappear without a proper alternative.

    Firebase Studio is being shut down without a true replacement, and that is a serious mistake.

    For many of us, Firebase Studio was not just an experiment — it was a practical, browser-based development workspace deeply integrated with Firebase, accessible from anywhere, and useful for real production workflows.

    The alternatives being pointed to are not equivalent:

    Google AI Studio is more of an AI playground than a full development environment.
    Antigravity appears to require high-end local hardware, which defeats the purpose of a cloud-based workspace you can use from any machine.
    Firebase Studio gave developers something extremely valuable: flexibility, accessibility,… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Shamefull

    Its literally very much shameful how google operates. I tried multiple times to buy google cloud, google studio, and firebase but each time what i see is they deduct 2 Rs and set autopay but decline that you were not able to set your payment method. I tried this so many times but got the same results. if you guyz don't accept upi then why you give option to select. its really very upsetting. how can i trust you guyz when you take 2 Rs multiple times and doesn't validate the autopay then how can i be assured that you will not cut 15k as you set up the autopay for 15k and if i try that 10-20 times to setup autopay then ........ its really out of the mind kind of thoughts that coming in my mind. because who can expect google doing golmaal. such a shame

    Its literally very much shameful how google operates. I tried multiple times to buy google cloud, google studio, and firebase but each time what i see is they deduct 2 Rs and set autopay but decline that you were not able to set your payment method. I tried this so many times but got the same results. if you guyz don't accept upi then why you give option to select. its really very upsetting. how can i trust you guyz when you take 2 Rs multiple times and doesn't validate the autopay then how can i be assured that you… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Firebase Studio  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. كتابه
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  App Distribution  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating