Contact person: Business Client

Phone:Show

Email:Show

Location: Saint Thomas, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I already have a working ride-hailing stack: Laravel for the backend, Flutter for both rider and driver apps, MySQL as the data store, plus Composer and Node.js for dependency management and builds. The full source code lives in Dropbox and I will share access as soon as we start.

What I now need is a clean, end-to-end implementation of driver rules. Think of simple but important items like “no smoking”, “no pets”, or any future rule I decide to add. This feature touches four parts of the product:

• Database – (extend an existing one) so I can add, edit, activate, or archive rules at any time without further code changes.
• Admin panel – show the current rule set in a readable list and give me CRUD controls; this is where I will manage the content.
• Driver app – Driver selectable rules under their vehicle link in their account.
• Rider app – display the selected rules right before a passenger confirms a ride so expectations are clear on both sides.

At this stage I don’t need automated push, email, or in-app alerts for rules; simply making the rules visible in the stated locations is enough.

Deliverables that will let me sign off:
1. Updated MySQL schema and migration files.
2. Revised Laravel controllers/models plus any new API endpoints.
3. Flutter code changes for both apps with concise comments.
4. Admin panel interface adjustments matching the current UI style.
5. A short read-me that tells me where the new code lives and how to deploy it for future updates.

If you spot a smarter approach than the one outlined, I’m open to suggestions—just walk me through your reasoning." (client-provided description)