Contact person: Business Client

Phone:Show

Email:Show

Location: Basywater, Australia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need a clean, reliable mobile app that Prolux electricians can carry onsite to run emergency- and exit-lighting inspections in commercial and industrial buildings. The core workflow is simple: select the site, walk through each fitting, log pass / fail results, and capture notes or photos if needed. Once the round is finished the technician taps “complete” and the data syncs instantly to the cloud.

Key requirements
• Cross-platform: one code-base that runs smoothly on both iOS and Android phones or tablets.
• Testing & logging: intuitive forms that let users start a test run, record readings or faults, and save them even when offline, with automatic sync when connectivity returns.
• Report generation: on demand, the app should compile the latest results into a tidy PDF or Excel report we can email straight to clients or store internally.
• Roles & permissions: at minimum an Admin role (create sites, manage users, view all data) and an Electrician role (record tests, view only assigned sites). The structure must be flexible so I can add other roles later if needed.

Tech stack is up to you; Flutter, React Native or Kotlin / Swift with a common backend are all fine—as long as the final product is fast, secure and easy to maintain. Please include in your proposal:
1. Your recommended framework and why.
2. A brief outline of the database and report-generation approach.
3. Estimated timeline to a functional MVP and to full release.

I’m ready to start as soon as I find the right partner who can demo similar work and commit to clear, milestone-based progress.


OVERARCHING OBJECTIVE:

1. User & Site Information Collection:
• Capture the site name and address.
• Capture Client name
• Record the electrician’s name and the test date.
• Note that tests are performed every six months.

2. Initial Asset Register Setup:
• Build an asset register for each site, assigning a unique ID to each fitting.
• Document the fitting’s location, floor level, type (via a dropdown with the seven fitting types and the ability to add new fittings to the drop down list), and the switchboard it’s connected to.

3. Recording Test Results:
• For each fitting, record the start time, test duration, and whether it passed or failed.
• Technicians sign off once all fittings are tested.

4. Document Library and Client Access:
• Save test results in a document library organized by client and then by site address (e.g., Dexus → 360 Collins Street).
• Ensure clients can only access their own site’s test results for confidentiality.

5. Subsequent Tests and Version Control:
• Allow technicians to create new test entries without rebuilding the asset register.
• Technicians can update fitting details (like location or ID) if they change between tests.
• All test results are saved as new dated entries, maintaining a historical record." (client-provided description)