Clientè is a luxury client management platform built for high-value service businesses, focused on scheduling, governance, and compliance-first system design. Engineered for clarity, control, and long-term scalability.
This repository includes a local Flutter SDK at .flutter/flutter.
Use scripts/flutterw so commands work even when flutter is not on global PATH.
To initialize platform folders (Android/iOS) and get dependencies, run in the project root:
scripts/flutterw create .
scripts/flutterw pub getRun on an Android emulator or connected device:
scripts/flutterw devices
scripts/flutterw run -d <device-id>To build an APK for testing on a phone:
scripts/flutterw build apk --debugIf you want me to generate Android/iOS native folders here, I can run flutter create . for you — but the dev container may not have Flutter installed. If you want, I can instead provide a complete generated project structure.
The app includes a login screen with Firebase Authentication. Test credentials are pre-filled:
- Email: reviewer@cliente.app
- Password: Review@12345
Before running the app, configure Firebase:
-
Create a Firebase project at https://console.firebase.google.com
-
Add an Android app to your project and download
google-services.json -
Place
google-services.jsoninandroid/app/ -
Install FlutterFire CLI:
dart pub global activate flutterfire_cli
-
Configure Firebase in your Flutter project:
flutterfire configure
This will update
lib/firebase_options.dartwith your Firebase credentials. -
Create a test user in Firebase Console → Authentication:
- Email:
reviewer@cliente.app - Password:
Review@12345
- Email:
After setup, the app will show a login screen. Use the test credentials above to authenticate.
I created a placeholder upload keystore at android/app/upload-keystore.jks and a android/key.properties file with placeholder passwords. Replace these passwords and the keystore with your secure upload key before publishing.
Steps to produce a Play-ready AAB and upload:
# (1) Validate local Flutter SDK
scripts/flutterw --version
# (2) Generate platform folders if you haven't already (run locally)
scripts/flutterw create .
scripts/flutterw pub get
# (3) Verify the Android package name is set in
# android/app/src/main/AndroidManifest.xml (package="com.client.scheduler")
# (4) Build an Android App Bundle for Play
scripts/flutterw build appbundle --release
# (5) Upload the generated .aab from build/app/outputs/bundle/release/ to the Play ConsoleNotes:
- I previously created a placeholder keystore but removed it from the repository to avoid committing secrets. Do not commit
android/key.propertiesor any.jksfiles. - Use the GitHub Actions workflow secrets (
ANDROID_KEYSTORE_BASE64,ANDROID_KEYSTORE_PASSWORD,ANDROID_KEY_PASSWORD,ANDROID_KEY_ALIAS) to provide signing material to CI.
If you want me to attempt running flutter create . and/or generate the full Android Gradle wrapper here, I can try — but the container currently lacks the Flutter SDK.
I added a GitHub Actions workflow to build an Android App Bundle automatically: .github/workflows/android-build.yml.
Usage notes for CI:
- To let the workflow sign with your keystore, add a secret
ANDROID_KEYSTORE_BASE64containing the base64-encoded keystore, and these secrets:ANDROID_KEYSTORE_PASSWORD,ANDROID_KEY_PASSWORD,ANDROID_KEY_ALIAS. - The workflow will produce an
.aabartifact you can download from the workflow run.
Local helper scripts:
scripts/prepare_local.shwill runflutter create .andflutter pub get(requires Flutter installed locally).scripts/encode_keystore.sh <path/to/keystore.jks>base64-encodes a keystore file so you can paste it into the GitHub secretANDROID_KEYSTORE_BASE64.