The VisionScaper phone app is the field and office companion to the Contractor Hub on your website. It is built with React Native and Expo and draws real phone screens, not a website inside an app. Your website stays the one source of truth. The app has no database of its own.

• A copy of the person’s next days of jobs, so they can keep working with no signal.
• An outbox of taps the website has not confirmed yet. Unsent or refused changes are always shown on screen.

Some things are never queued offline: customer, lead, schedule and route changes, plus anything that sends a message or touches money. Offline, those screens say so. This is deliberate, so a retry hours later cannot overwrite someone else’s change.

The website decides which phone a person gets, from their team role.

Which tabs an office person sees also depends on their permissions and on the “Show me” Simple or Full setting. Details are in the related articles.

• Jobs by day, a running timer, status buttons, checklists, photos, materials and issue reports (see [crew-app-my-day-time-messages]).
• Customers, properties, new leads, the calendar and dispatch (see [phone-app-clients-schedule-dispatch]).
• Quotes, invoices, payments received and expenses (see [phone-app-quotes-invoices-money]).
• Tasks, reports and weather (see [phone-app-tasks]).
• Approving customer messages and voice notes (see [phone-app-customer-messages-and-voice-notes]).

Work the app does not do yet opens in the Contractor Hub in a signed-in browser.

You do not build the app inside WordPress. The app’s source folder has a file called BUILD.md that walks through it. In short:
1. You need an Expo account (builds run on Expo’s servers, so no Mac is needed).
2. An iPhone install or App Store release needs an Apple Developer account. Google Play needs a Google Play Console account. Follow each company’s current sign-up instructions and check current fees.
3. Builds are started with the eas build command, for example eas build -p android --profile preview. BUILD.md lists the profiles.
4. Push notifications go through Expo to Apple and Google. In WordPress go to Settings → VisionScaper, find Mobile app (push notifications), and paste an Expo access token only if “enhanced push security” is turned on in your Expo project. Otherwise leave it blank.

Note: when BUILD.md was written it said no installable build had been made and nothing had been run on a real phone. Check the file for the current status before you promise the app to your crew. (Not verified in code.)

Warning: the launch checklist says the app’s bundle ID and site address must be settled before the first store submission, because they cannot change afterward.

• Turn on the optional AI features on the same settings screen only if you want them: Voice-note summaries, Estimate from a recorded walk, and Automatic payments (autopay). Each is off until you tick it.
• Tell your crew the phone needs an https website to sign in.

• A screen is missing: the app hides screens the website’s plugin version cannot serve, and screens the person’s role cannot use. Check the plugin is current and the role’s permissions.
• Sign-in trouble: see [phone-app-sign-in-and-devices].

• Signing in to the phone app and managing signed-in phones
• The crew app: My day, Time and Messages
• Customers, schedule and dispatch on the phone
• Quotes, invoices, payments and expenses on the phone