01
Customer photo intake
Let customers choose photos to attach to an inspection, claim, or service request.
Productivity
Build more with Google Photos.
Let users pick photos from their Google Photos library via the Google Photos Picker API. Shape those capabilities into a system that fits your team.
Build concepts, not preinstalled apps. Provider plans, permissions, and API availability apply.
The possibilities
What could you build?
02
Project reference gallery
Organize user-selected images beside project notes and approvals.
Start with the customer photo intake.
Keep the first version small enough to test with the people who will use it.
- 01Google Photos
- 02Customer photo intake
- 03Reviewed next action
- 01
Choose the first job
Use the first idea as your brief: Let customers choose photos to attach to an inspection, claim, or service request. Name the person responsible and the information they need to act.
- 02
Confirm access before connecting
Use the user-driven Picker flow. Do not promise background access to a person's entire photo library.
- 03
Shape the app with Scout
Use the starter prompt below. Ask Scout to propose the records, source field mapping, views, and access rules. Preview sample data before connecting Google Photos; keep source IDs so records stay traceable.
- 04
Pilot, then expand
Test with a small approved dataset and a least-privileged user. Check missing records, revoked access, repeated events, and failed requests. Enable live writes or messages only after the responsible owner approves the workflow.
Start with this prompt
Paste into Scout, then adapt it to your team. Do not paste credentials or private customer data.
Create this app with Google Photos: Customer photo intake. Let customers choose photos to attach to an inspection, claim, or service request. Start with sample data and a small, approved set of records. Before connecting live data: Use the user-driven Picker flow. Do not promise background access to a person's entire photo library. Propose the data model, access rules, and source-to-app field mapping before implementation. Add source links, a last-updated time, and clear empty and connection-error states. Keep credentials out of client code. Require human approval for external messages, source changes, or money movement. Test duplicate events, revoked access, and recovery before publishing.
Make it work your way.
Start with Scout, or map the first build with our team.