Skip to main content

Content and Data Setup

The mobile app should never open to empty screens unless that is intentional. Use the admin panel to prepare the Firebase records and media assets that make the first production build useful: categories, products, listings, providers, restaurants, posts, email templates, campaign assets, and support accounts.

Setup Order

Follow this sequence:

  1. Configure Firebase and admin roles.
  2. Upload reusable media assets.
  3. Create core taxonomy, such as categories, filters, tags, or car types.
  4. Add the primary business records for the app type.
  5. Add templates for email or push campaigns if enabled.
  6. Run the React Native app and verify list, detail, search, and empty states.
  7. Export CSV snapshots for review before production.

Media Library

Use Media Library for assets that may be reused across the app:

  • product photos;
  • category images;
  • listing images;
  • restaurant and provider images;
  • placeholder profile photos;
  • campaign banners;
  • onboarding or marketing images;
  • social content test media.

After upload, copy the returned URL into the relevant entity form. The uploaded file is stored in Firebase Storage through a protected admin route.

Starter Data By App Type

App familyMinimum useful data
CommerceCategories, products, product images, order test user, email templates, payment settings.
Food deliveryRestaurants, menus, products, delivery users, order statuses, restaurant images.
Single vendorRestaurant profile, catalog categories, products, delivery settings, reservations if used.
AppointmentsService categories, providers, professionals, service pricing, sample bookings, reviews.
TaxiCar categories, pricing rules, driver users, vehicle data, payment methods, sample trips.
ListingsCategories, filters, listings, map coordinates, listing images, reviews, saved listing checks.
Social appsUsers, posts, stories, comments, reports, featured content, notification samples.
DatingComplete profiles, photos, gender preferences, location data, reports, swipes, matches.
ChatUsers, conversations, messages, support escalation examples, notification tokens.
GPT ChatUsers, assistant conversations, support workflows, usage review samples.
Video ChatUsers, conversations, AV call records, call status records, connection data samples.

CSV Import

Use CSV import when you need to prepare larger catalogs or operational datasets.

Recommended process:

  1. Create one record manually in the admin panel.
  2. Export the entity CSV.
  3. Use the exported columns as the import template.
  4. Import two or three rows first.
  5. Review the records in the admin panel and the mobile app.
  6. Import the full dataset only after the small import is correct.

Keep these rules in mind:

  • use stable IDs only when you need predictable document IDs;
  • keep image URLs valid and publicly readable by the app;
  • preserve enum/status values expected by the mobile app;
  • avoid placeholder text in fields shown in the mobile app;
  • check required map coordinates for listing and taxi flows;
  • test one imported record on device before importing hundreds of records.

CSV Export

Use CSV export for:

  • catalog review;
  • launch readiness checks;
  • operational reporting;
  • support review;
  • QA snapshots;
  • operational snapshots for the team;
  • backup before bulk changes.

Exports are especially useful before bulk hide/show, approval, status, or catalog changes.

Entity Quality Checklist

Before production, important records should have:

  • readable title or display name;
  • complete description where the mobile UI shows one;
  • at least one image if the mobile UI expects media;
  • category, type, or filter assignment;
  • owner, author, provider, vendor, or driver assignment when required;
  • valid status value;
  • price, currency, or booking details where relevant;
  • map coordinates for map-based apps;
  • no demo names, lorem ipsum, or broken image URLs.

Verify In The Mobile App

After adding data:

  1. run the React Native app;
  2. open the home screen;
  3. inspect list screens and detail screens;
  4. test search, filters, maps, checkout, booking, messaging, or posting flows depending on the app;
  5. create a record from the mobile app;
  6. confirm the record appears in the admin panel.

Next Steps