Is there anything DEV3 Beadwell does not do?

Good to know

• The washer app has no device GPS plugin. Against a real server it reports the last position the server holds, so a real washer cannot pass the 150 m arrival check until you plug a location source into the app (locationSourceProvider, described in data/location.dart).
• The customer app books by card only. The API accepts cash, but the app does not offer it.
• The mid-job add-on is not built. There is no route for a washer to add an extra service in the middle of a job.
• There are no app store links yet. The store buttons on the website point to the apps section of the page, and the two phone mock-ups on the site are drawn in CSS, not real screenshots.
• The apps' real-backend runs are automated tests. Both apps were run against a live server through test files, not by hand on a device. Sign-in is throttled, so do not loop them.
• A few washer screenshots clip their last line behind the action button (offer taken and photos missing), and the complete screen has an empty middle. These are cosmetic.
• Water and photos need real hardware to prove. The van water limits and the corner photo guide were exercised with demo data and the simulator, not with real vans.
• Payments, SMS and push are simulated by default. The simulated payment 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.
• 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 Pest tests run on SQLite, where row locks do nothing; the concurrency checks that prove the locking run on MySQL 8.
• Name: Beadwell 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, business and record in the screenshots is fictional. Install it with the demo data to try every role on your own server.