Is there anything DEV3 Kerbora does not do?

Good to know

• Stored-card charging is simulated only. Card payments work on the simulated gateway. Charging a saved card with Stripe, Razorpay or PayPal is not built, so a developer has to add it, and there is no pre-authorisation. Real push and payment gateways were never called.
• The driver app has no GPS plugin. Positions come from a built-in trip simulator. For real driving you need to add a location plugin to the driver app (the app reads positions through one provider you can replace) and connect a map provider.
• Masked calling is a stub. The call button exists but does not connect a real masked number: add your telephony provider.
• The driver home screen scrolls slightly on small phones. On a 390 by 844 phone the dials and rows fit above the tab bar, but on shorter screens the home screen scrolls a little.
• A driver cancelling in the last matching round ends the search. A driver cancel on round 5 goes straight to no driver found, and every driver who was already offered stays excluded. This was left as an open product decision.
• Languages: the marketing site and the passenger app include a right-to-left Arabic layout. The admin and dispatch panels were not translated.
• The apps were not tested on physical devices. They build as debug Android packages and run on the iOS simulator.
• Use MySQL or MariaDB on a live site. The concurrency checks run on MySQL 8.
• Name: Kerbora is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• No hosted demo. The city, drivers and passengers in the screenshots are fictional.