bookslot-mobile
Flutter customer app for booking appointments and paying a deposit.
~/problem
A booking backend needs a real client to prove its public API works end to end on a phone, without exposing any real business data.
The public, demo-facing half of the bookslot pair. It browses a seeded demo studio's services and availability, books a slot, takes a Stripe test-mode deposit and schedules a local reminder. It talks to bookslot's real public booking API, not a mock.
~/highlights
- Pointed at bookslot's production-shaped public API with a seeded demo tenant; API base URL, tenant slug and Stripe key are build-time --dart-define values.
- Stripe deposits in test mode only, via flutter_stripe.
- Local appointment reminders through flutter_local_notifications; tests use a fake scheduler because the real plugin fails in plain flutter_test.
- CI runs dart format, flutter analyze (zero issues required) and flutter test with coverage, plus a security workflow.
- A separate Android workflow builds the app and runs the integration test on an emulator, including a reboot-survival check for reminders using a probe APK driven by adb.
- Scope limits are documented: no admin features, no real push, no live Stripe credentials, no self-service cancel.
~/architecture
- Flutter app → API client, Stripe SDK, Local notifications
- Services list, availability, booking flow, my bookings, reminders.
- API client → bookslot API
- HTTP client for bookslot's public tenant booking endpoints.
- Stripe SDK → bookslot API
- Collects the deposit in test mode.
- Local notifications
- Schedules reminders on the device.
- bookslot API
- The Laravel backend in the paired repository.
~/stack
- Flutter
- Dart
- Provider
- flutter_stripe
- flutter_secure_storage
- flutter_local_notifications
~/status
Public demo client, MIT licensed. Unit and widget tests run in CI; the emulator integration test is not part of the default CI run.
~/related
- bookslot Booking, deposits and no-show protection for appointment-based businesses.