Product owners need to click through a new citizen self-service UI before merge. The front end is an Amplify app on a feature branch. What should they use?
Select an answer to reveal the explanation.
Short Explanation
Preview branch is the sidewalk model of the new permit desk—walk it before remodeling City Hall. Amplify branch preview URLs give product a real hosted look without merging to prod. Laptop screen-shares and Downloads-folder HTML are shaky substitutes.
Full Explanation
Product owners reviewing a new citizen self-service UI on an Amplify feature branch should open the Amplify preview URL for that feature branch environment to review the UI in isolation. Branch previews give municipal product owners a clickable environment without merging to main or reviewing only after public production deployment. Isolated preview artifacts are the intended Amplify workflow for front-end acceptance.
Merging to main first, then reviewing only after the change is on the public production site fails by forcing incomplete UX onto citizens before product acceptance. Emailing a zip of static files and asking reviewers to open index.html from Downloads fails conceptually—local files miss hosting paths, auth callbacks, and CDN behavior. Disabling Amplify hosting and requiring reviewers to run the React app only on a developer's laptop over screen share fails as a non-scalable, non-shareable review path.
Exam caveat: preview backends and Cognito app clients must be non-production so product clicks cannot alter live citizen accounts. Operational check: open the branch preview URL, complete the self-service click-path checklist, capture feedback against the branch, and merge only after acceptance.