Introduction

Welcome to the official documentation for the Logo Quiz app — a complete, production-ready Flutter source project for Android and iOS, distributed on CodeCanyon by Visuella.

Logo Quiz is a polished, category-based trivia game where players identify brands and logos across dozens of themes. It ships as a full source project you can rebrand, customise and publish under your own developer account, within the terms of the CodeCanyon license you purchased (Regular or Extended). Buyers get lifetime free updates and no runtime dependency on a third-party backend from us.

Heads up — third-party service costs. The app is fully functional out of the box, but a few features rely on external services owned by third parties: Google AdMob, AppLovin Max, and Google Firebase (Analytics, Crashlytics, Auth, etc.). Depending on your usage volume, these services may incur external costs charged directly by their providers — for example, Firebase can move from its free Spark plan to a paid Blaze plan once you exceed the free quotas, and ad networks may charge processing fees on your earnings. These costs are set by Google / AppLovin and are not included in the CodeCanyon purchase price. Review each provider's current pricing before enabling the feature. Every relevant page in Services links to the provider's pricing page.

Who this documentation is for

These pages are written for buyers who want to configure and publish the app without touching the Flutter source code. The app ships with a browser-based setup GUI that writes every configuration key for you — app identifiers, Firebase, ads, in-app purchases, Play Games / Game Center, logging, and more — so most of the work is filling in fields rather than editing files.

Some experience with Android Studio, Xcode and the app-store publishing flows is still useful, but no Flutter or Dart knowledge is required to ship the app as-is.

What you'll find here

The documentation is organised into five sections:

1. 01
   Get Started What the project is and the tools to install first.
2. 02
   Installation Environment file, setup page, app IDs, signing key, Firebase.
3. 03
   Customisation Trivia data, app icon, images & animations, languages.
4. 04
   Services AdMob, AppLovin Max, in-app purchases, Play Games, logging.
5. 05
   Publishing Building for the stores, and upgrading to a newer version later.

Follow the sections in order for a first-time build. If you're returning to update or extend an existing app, jump straight to the section you need — each page is self-contained.

First-time installation — follow this order

If this is your first build, work straight down this list. Every page assumes the ones above it are already done, so going out of order is the most common way to get stuck.

1. Get Started → Prerequisites — install Flutter, the Android SDK, Xcode and the Firebase tools. Nothing below works until flutter doctor is green.
2. Installation → Environment — create your .env file from the template.
3. Installation → Setup Page — open setup.html, the browser screen that fills .env in for you.
4. Installation → General — app name, version, coin economy, ad pacing, daily reminder.
5. Installation → App IDs — your Android package name and iOS bundle ID. Choose carefully — these can never change once the app is published.
6. Installation → Android Signing Key — generate the keystore and back it up. Required for every Play Store upload.
7. Installation → Firebase — connect the app to your own Firebase project.
8. Customisation — trivia data, app icon, images & animations, languages. Optional, and the four pages can be done in any order.
9. Services — AdMob or AppLovin Max, in-app purchases, Play Games, leaderboards, achievements, logging. Optional — enable only the features you actually plan to ship.
10. Publishing → Build & Publish — build the signed release and upload it to Google Play and the App Store.

The one habit to keep. After saving anything on the Setup Page, run make sync in the project root before you rebuild. Skip it and your changes stay in .env without ever reaching the app.