What You're Setting Up

Learnify LMS is one Laravel backend and one database with two faces on top of it: the website (storefront, student area, instructor workspace and admin panel), and a Flutter Learnify LMS App for Android and iOS, used by students and instructors. Set up the backend first — the app points at its API.

The download contains two folders:

Folder	What it is
WebSourceCode	The Laravel 13 application — upload this to your server.
AppSourceCode	The Flutter project, with the Android and iOS projects inside.

Setup Order

Do the backend first. The app needs the API to be live and reachable over HTTPS before it can log anyone in.

Stage 1 · Web Backend (Laravel)

Upload the WebSourceCode folder to your server, point the domain at its public directory, then open /install in a browser. The wizard does the rest — there is no command line step required. Full detail is in the Web Panel guide.

1. Check the server

   PHP 8.3+, MySQL 8.0+, URL rewriting, allow_url_fopen. The installer verifies each item on its first screen and tells you what is missing.

2. Create an empty database

   One database and one user with full rights on it. Do not create any tables — the installer does that.

3. Run the installer

   Open https://yourdomain.com/install. Enter the database details, then your admin name, email and password.

4. Log in and follow the setup wizard

   Name, logo, language, currency, the kind of academy and your payment details, then the Getting started list on the dashboard. No cron job is needed; add one later only for exact timing.

5. Set up mail and storage

   SMTP so registration, receipts and password resets arrive; local or S3-compatible storage for uploads.

6. Connect a payment gateway

   Stripe, PayPal, SSLCommerz or manual bank transfer. Add your keys under Payments → Payment Gateways and press Test keys where the card has it. Stripe and Razorpay also need the webhook address shown on their card added in their own dashboard.

First Login

After the installer finishes, sign in with the admin account you just created. You land on the dashboard; the sidebar is grouped by what you are doing — Manage, Sales, Finance, Marketing, Content, System, Organization.

Stage 2 · Mobile App (Flutter)

The app is a normal Flutter project. You only have to tell it where your API lives, then set the name and icon. Everything else — colours, logo, splash — comes from your admin panel at runtime.

1. Install Flutter

   Flutter 3.44 stable (Dart 3.12). Android Studio for Android builds; Xcode on macOS for iOS.

2. Point it at your site

   Set API_URL to your HTTPS domain. It is a --dart-define, so you never edit source to change environments.

3. Set the app identity

   Application id / bundle id, display name and launcher icon — the three things you cannot change after publishing.

4. Add Firebase (optional)

   Only needed for push notifications. Drop in the two config files and enable push in the panel.

5. Build a release

   An App Bundle for Play, an archive for the App Store. Test the debug build against your live API first.

Customization

Everything below is yours to change before you publish — the item ships with a neutral Learnify identity so it never fights your own brand.

What	Where
App display name	Android: android:label in android/app/src/main/AndroidManifest.xml. iOS: CFBundleDisplayName in ios/Runner/Info.plist. Full steps in Mobile App → App Name, Id & Icon.
Application id / bundle identifier	Android: applicationId and namespace in android/app/build.gradle.kts. iOS: the bundle identifier in Xcode → Signing & Capabilities. Ships as com.learnify.lms; change it to your own reverse-domain id before your first store upload — it cannot be changed afterwards.
Launcher icon	Replace the source image under assets/ and run flutter pub run flutter_launcher_icons.
Colours & logo (website)	Admin panel → Settings → Appearance: presets, colours, font, sidebar, with a live preview. See Web Panel → Settings.
Colours, logo & splash screen (app)	Admin panel → Settings → Mobile App. The app reads /api/v1/config on every launch and repaints itself with your site colours; App logo is a separate square mark for the app (512×512 PNG/WebP recommended) that appears on the splash screen, the home header and the login screen — leave it empty and the app falls back to the site logo. No rebuild needed; only the display name, bundle id and launcher icon above need one. See Mobile App → Colours & Logo.

Launch Checklist

Work down this list before you send anyone to the site.

• APP_DEBUG=false and APP_ENV=production in .env.
• HTTPS on, with APP_URL set to the https:// address.
• Background tasks are running — System → Health shows the scheduler as running on site visits or from your cron. Add the cron entry if reminders and campaigns must go out at the exact minute on a quiet site.
• A queue worker is running under Supervisor if you use campaigns or large exports.
• SMTP tested: register a throwaway account and confirm the email arrives, then buy a course and confirm the receipt and enrolment welcome arrive too.
• Invoice details filled in under Settings → Contact; decided whether new instructors need approval (Settings → Commerce).

• Optional: Zoom Server-to-Server credentials under Settings → Live classroom so live classes create their own meetings.
• A payment gateway is live, its keys pass Test keys, its webhook is registered (Stripe, Razorpay), and a real low-value purchase shows the order as paid.
• The default admin path has been changed and two-factor authentication is on.
• Terms, privacy and contact pages have your own content.
• Currency, tax rules and instructor commission match what you actually intend to charge.
• Scheduled backups are configured and one restore has been tested.
• Push tested on a real Android and iOS device (iOS needs the APNs key).