Policy Hub Android app

Overview

The Policy Hub Android app is the companion of the Policy Hub SaaS website. Customers see their policies, pay premiums, file claims, chat with their agent and keep a policy card on their phone.

One app serves every agency on your platform: the customer finds their agency by name, company code or QR code, and signs in. You can also build an own-brand app for a single agency.

What is in the package

Features

Everything a policyholder needs, in one app.

Not included

• Owner, agent and staff tools. Agencies manage everything on the website; the app is for customers only.
• Card payments inside the app. Payment opens the agency's own gateway page.

Requirements

Your computer (to build the app)

• Flutter (a current stable release whose Dart is 3.13 or newer)
• Windows, macOS or Linux with Android Studio and the Android SDK
• About 10 GB of free disk space

Phones

• Android phones and tablets supported by your Flutter version

Accounts

• Google Play developer account (one-time fee) to publish
• Optional: a Firebase project for push notifications

Website

• Policy Hub SaaS v1.7 or newer on https
• The agency's website published (the company code is the name in its address, /site/<code>)
• Email (SMTP) set up if you want emailed sign-in codes
• The cron job running, for reminders and push

Install Flutter & Android Studio

1. Install FlutterFollow docs.flutter.dev for your system and add flutter to your PATH.
2. Install Android StudioInstall it with the Android SDK, the command-line tools and an emulator image. Accept the licences: flutter doctor --android-licenses.
3. CheckRun flutter doctor. Every line for Flutter and Android should have a green tick.

Prepare the website

Do this once, before you test the app.

1. Use httpsThe app talks to your website over https. A debug build also accepts plain http for testing.
2. Publish the agency's websiteUnder Website the agency switches the website on. The company code is the name in the website address.
3. Open Mobile AppsThe owner's Mobile Apps page shows the QR code, the company code and the page customers use to get the app. The super admin saves the store links there once the app is published.
4. Run the migrationAfter uploading the website, run php artisan migrate so the chat tables and permissions exist.
5. Set up emailUnder Settings → Email Settings. It is used for emailed sign-in codes and reminders.
6. Add the cron line* * * * * cd /path/to/site && php artisan schedule:run >> /dev/null 2>&1 so reminders and push messages go out.
7. Create a test customerAdd a customer on the website, or let one register online. The customer signs in to the app with the same email and password.

Set up the project

1. UnzipUnzip policy-hub-android-v1.0.0.zip and open the android_app folder in Android Studio or VS Code.
2. Get the packagesIn that folder run flutter pub get.
3. Check the codeOptional: flutter analyze and flutter test.

cd android_app
flutter pub get

Run on a phone or emulator

Pass your website address when you run or build, so customers never type it.

On a real phone

1. Turn on USB debuggingSettings → About phone → tap Build number seven times, then Developer options → USB debugging.
2. Connect and checkPlug the phone in and run flutter devices.
3. Runflutter run --dart-define=API_BASE_URL=https://yourdomain.com

On the emulator

Start an emulator from Android Studio, then run the same command. To reach a website on your own computer the emulator uses http://10.0.2.2/... instead of localhost.

flutter run --dart-define=API_BASE_URL=http://10.0.2.2/your-folder/main_file

Testing against a local website (http)

A debug build accepts plain http://. Release builds need https://.

Quick check without a phone

This signs in and out against your website using a customer account and reads the data the app needs:

dart run tool/smoke.dart https://yourdomain.com company-code customer@example.com password

How customers connect

After that the sign-in screen shows the agency's logo and name, and the whole app takes on its colour. A phone can hold several agencies (More → Switch company).

An app for one agency only

Build with the agency's code as well and the app has no company screen:

flutter build apk --dart-define=API_BASE_URL=https://yourdomain.com --dart-define=COMPANY=company-code

Sign-in & security

Branding & customisation

Changes that need no new build (from the website)

• The agency's logo, name and colour: the app takes them from the agency's website settings.
• The QR code, company code and store links on the Mobile Apps page.
• Whether emailed codes and the assistant are available.

Changes in the code (then build again)

Push notifications (Firebase)

Optional. Without it the app works and the in-app inbox still fills up; only the phone pop-ups are missing.

1. Create a Firebase projectAt console.firebase.google.com add an Android app with your application id.
2. Add the fileDownload google-services.json and put it in android/app/. The build switches push on when the file is there.
3. Connect the serverProject settings → Service accounts → generate a private key. On the server put its path in .env as FCM_CREDENTIALS=/path/key.json.
4. Check the schedulerThe Laravel cron line must be running; reminders are sent from it.

When customers are notified

• Before and after an instalment or renewal is due (reminders)
• A payment is received
• A claim changes status or needs a document
• The agency replies in the chat
• A request is answered

Signing key & build the release

1. Create a signing key (once)

keytool -genkey -v -keystore ~/policy-hub.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload

2. Tell the build where the key is

Create android/key.properties with:

storeFile=/home/you/policy-hub.jks
storePassword=********
keyAlias=upload
keyPassword=********

3. Build

flutter build appbundle --dart-define=API_BASE_URL=https://yourdomain.com

Upload build/app/outputs/bundle/release/app-release.aab to Google Play.

A test APK to share

flutter build apk --split-per-abi --dart-define=API_BASE_URL=https://yourdomain.com

This makes smaller files, one for each processor type, in build/app/outputs/flutter-apk/.

Publish on Google Play

1. Developer accountRegister at play.google.com/console and pay the one-time fee.
2. Create the appAll apps → Create app. Choose the name, language, App and Free.
3. Store listingAdd the name, short and full description, the app icon (512×512), a feature graphic (1024×500) and phone screenshots.
4. App contentFill in the privacy policy link, ads declaration, data safety form (see below), target audience and content rating.
5. Upload and releaseProduction → Create new release → upload the .aab → add release notes → review and roll out. New developer accounts may be asked to run a closed test first.
6. Add the link to your websiteCopy the Play Store link into the website's Mobile Apps page (super admin) so the Get our app page shows the store button.

Updates

Raise the version in pubspec.yaml (for example 1.0.1+2; the number after + must go up every upload), build again and upload a new release.

Privacy & data safety

Use this when you fill in the store forms.

Android permissions used

The camera and photo picker are used through the system picker when the customer uploads a document or sends a picture, so no extra permission is declared.

Data the app handles

Settings reference

android/app/src/main/AndroidManifest.xml

• The three permissions above
• android:label: the app name
• A policyhub://connect link so a scanned QR code opens the app
• applicationId and namespace in android/app/build.gradle.kts; the Firebase plugin is applied only if google-services.json exists

Code structure

The iPhone project in the other package has identical lib/ code; when you change one, make the same change in the other.

Updating to a new version

1. Back upKeep your own changes (name, id, icons, colours) somewhere safe.
2. ReplaceUnzip the new package and copy your changes over it.
3. Raise the versionIncrease version in pubspec.yaml.
4. Build and uploadBuild the release again and upload it to Google Play.

Update the website to the version the new app needs first.

Troubleshooting & FAQ

Do I need one app per agency?

No. One app serves every agency; the customer picks theirs. You can also build an own-brand app for a single agency.

Can owners and agents use the app?

No, it is for customers. Agencies and agents use the website.

Where is the data stored?

On your website's server. The app keeps the sign-in token, and the offline policy cards, only on the phone.

How do payments work?

The app opens the agency's own payment page in a secure in-app browser. No card details pass through the app.

Can I publish under my own name?

Yes. Change the name, id and icons, then publish with your own Google Play account.

Support

Open a ticket at support.smartwebinfotech.com with your purchase code, the app version, what you did and what you saw.