Planny
Production platform for driving schools: student management, lesson booking, instructor scheduling, progress tracking, notifications, and multi-role access.
Flutter, iOS, Android
An app that is mostly complete needs a focused recovery plan. I review build failures, broken journeys, dependencies, and backend configuration before deciding what should change.
Send me the current repo state and blockersRecord the Flutter and Dart versions, package lockfile, Xcode setup, and Android build configuration. Establish the last reproducible build. An unrelated dependency upgrade can turn one failure into several and obscure the original cause.
Platform permissions, signing, notification configuration, and plugin setup deserve their own checks. Reproduce the failing journey on the affected platform and distinguish a build failure from a runtime integration failure.
Review authentication, Firebase or Supabase configuration, API contracts, and payment completion as applicable. Verify Stripe or RevenueCat state against the backend rather than only the success screen. Isolate staging, fix the highest-risk blockers, and regression-test critical journeys before submission.
Production platform for driving schools: student management, lesson booking, instructor scheduling, progress tracking, notifications, and multi-role access.
Flutter, iOS, Android
Authenticated luxury fashion marketplace connecting buyers and sellers: catalogs, multi-role workflows, payments, orders, and logistics across Flutter for iOS, Android, and web.
Flutter, iOS, Android, Web
Yes. The review focuses on behavior, maintainability, and release risk. The origin of the code does not determine whether it should be kept.
That percentage does not show release risk. A build, known issue list, and walkthrough of the remaining journeys are needed for a useful estimate.