Is there anything DEV3 Mendfolk does not do?

Good to know

• Payments and push are simulated by default. The simulated gateway works out of the box, so booking and paying need no keys. Stripe, Razorpay and PayPal drivers are included but were not run against real accounts. Push notifications are logged, not sent, until you add FCM or APNs keys.
• Nothing is charged without the customer. Block payments and top-ups need the customer to tap and pay; there is no charge to a stored card. Billable time stops at the paid block and anything beyond it is shown as unbilled.
• Stripe refunds have no idempotency key yet. A gateway timeout after Stripe accepted a refund can be retried, so check your Stripe dashboard for duplicates and add a key in the driver before you take real card payments.
• The apps were not tested on physical devices. They build as debug Android packages and run on the iOS simulator. The arrival location check was compiled and run on simulators only, and it flags a far-away start for support but never blocks a job. The fixer sign-up screen was tested only against the app's built-in demo server.
• Updates are polled, not pushed. Chat and job status refresh about every 5 seconds. There is no offline queue for the timer, no customer signature and no barcode scanning.
• Some race paths are not covered by the parallel tests. A payment against a hold expiring, an accept against an offer expiring in the same second, two parallel starts and parallel dispute refunds are not in the MySQL race checks. The order in which rows are locked is covered by a test, but that test proves the order, not MySQL blocking.
• A failed extension has two rough edges. An overlap after a failed extension is flagged on the same task rather than on the next job, and a second top-up after a failed extension does not retry the cells that were missing.
• Rejecting a fixer application suspends the account. There is no separate rejected status. In demo mode some thumbnails (brief photos, Fix List items and receipts) are generated tiles.
• Photos. The website uses two stock photos and the apps' demo mode uses seven more, all taken from Pexels. DEV3 could not open the Pexels pages to confirm the photographer or the licence line of each photo, so check each photo's page, or replace the files in public/images/photos and apps/*/assets/photos, before you launch publicly.
• Use MySQL or MariaDB on a live site. The Pest tests run on SQLite, where row locks do nothing; the concurrency checks that prove the locking run on MySQL 8.
• Demo data takes time to load. About 8,000 tasks take roughly 40 seconds on MySQL and longer on a slow host. If the installer stops part way, raise the request time limit and install again on an empty database, or choose an empty install.
• Name: Mendfolk is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• No hosted demo. Every customer, fixer and record in the screenshots is fictional. Install it with the demo data to try every role on your own server.