Finalize Airtable Mobile Report Interface
Budget: $30 – $250 USD
Everything in my Airtable base is already built; I just need the mobile Interface Designer polished so technicians can finish their AC maintenance reports without friction. We’re working inside Airtable’s native mobile app, so all tweaks must live in Interface Designer—no external tools or scripts.
Scope you’ll handle right now
• Conditional visibility: hide or reveal specific group blocks depending on the “Service Type” field (Preventive vs Emergency). I haven’t provided explicit field maps, so you’ll infer which blocks belong to each service type and wire the show/hide rules accordingly.
• Multi-unit addition: drop in a Record List component tied to the Units table and activate the (+) button so a tech can add as many AC units as needed within the same Service Report.
• Auto-linking logic: each new unit created through that (+) drawer must automatically establish the correct linked-record relationship back to the open Service Report.
• Unit-specific fields: inside the add-unit drawer, surface fields conditionally based on the “Unit Type” selection (VRV vs Split) so techs only see what’s relevant.
Acceptance criteria
1. Toggling the Service Type field instantly updates visible groups without page reloads.
2. Clicking (+) in the Record List spawns a drawer where the Service Report link is pre-filled and locked.
3. Choosing VRV or Split immediately filters the drawer’s fields to the correct subset.
4. I can complete the full workflow on an iPhone and Android in less than three minutes without error messages.
All schema elements are finished; no database design is required. I expect this to be a quick, 1-to-2-hour session for someone fluent in Airtable Interface Designer. If you’re that person, let’s wrap this up today.
Scope you’ll handle right now
• Conditional visibility: hide or reveal specific group blocks depending on the “Service Type” field (Preventive vs Emergency). I haven’t provided explicit field maps, so you’ll infer which blocks belong to each service type and wire the show/hide rules accordingly.
• Multi-unit addition: drop in a Record List component tied to the Units table and activate the (+) button so a tech can add as many AC units as needed within the same Service Report.
• Auto-linking logic: each new unit created through that (+) drawer must automatically establish the correct linked-record relationship back to the open Service Report.
• Unit-specific fields: inside the add-unit drawer, surface fields conditionally based on the “Unit Type” selection (VRV vs Split) so techs only see what’s relevant.
Acceptance criteria
1. Toggling the Service Type field instantly updates visible groups without page reloads.
2. Clicking (+) in the Record List spawns a drawer where the Service Report link is pre-filled and locked.
3. Choosing VRV or Split immediately filters the drawer’s fields to the correct subset.
4. I can complete the full workflow on an iPhone and Android in less than three minutes without error messages.
All schema elements are finished; no database design is required. I expect this to be a quick, 1-to-2-hour session for someone fluent in Airtable Interface Designer. If you’re that person, let’s wrap this up today.