Handoff to Engineers

Hand off implemented UI changes as a pull request, where a developer can review the code before merging it into the team's project. Include a visual review to show what changed and steps to try it in the app.

If you have only explored an idea, build the chosen direction first. Your code hosting account must have access to the project's repository; Hexby prompts you if you need to connect or grant access.

Check the app

Open the project and branch containing your changes, then open Preview App. Check:

Desktop and mobile layouts.
Buttons, forms, and relevant loading or error states.
Other pages that use shared components you changed.

Select Open in browser beside the address bar to try the same page in your browser. A local address such as localhost works on your computer; use a shared review link for teammates.

See Preview App for help running the app.

Choose how to hand off

Review the design first

Choose Ship → Submit for design review.
Check the brief, before-and-after screens, and change notes.
Choose Send for review and invite your reviewers.
Address feedback and send an update if you make changes.
Once approved, choose Hand off to developers.

Reviewers open the shared link in their browser to comment or choose Approve all. If they open a received review in Hexby's desktop app, use Open in browser to leave feedback. See Visual Review for the full workflow.

Approval covers the version you sent

If you edited the code afterward, check which changes the handoff will include. Read remaining comments too: approval does not resolve them.

Hand off without design approval

Choose Ship → Handoff to Devs to send the code directly for developer review. Tell the developer that design approval is still needed.

Withdrawing a review deletes its comments

If a review is active, Hexby asks you to withdraw it first. Comments on a sent review are permanently deleted. Save any feedback you need elsewhere before continuing.

Check the repository, branch, and changed files, then complete the handoff. Selecting screens for the visual review does not limit the code included.

Open the pull request. An approved-review handoff includes the visual review link and approved screenshots when available.

Add the details your developer needs:

What changed and anything unfinished.
The page to open, steps to follow, and any test account or sample data needed.
What you checked and what still needs testing.

For example:

Updated the mobile registration layout. Open /signup, submit an empty form, then register with a test account. Errors should stay beside each field.

Checked in Chrome at mobile and desktop widths. Safari still needs testing. Visual review: [paste link], Version 2.0.

Send the pull request link to your developer. Confirm they can open both the code and visual review; each requires its own access. Creating the pull request does not merge the code or publish the app.

To reopen a pull request already created for a review, choose Ship → Handoff to Devs again.

For the developer receiving the work

Open the pull request and visual review in your browser. Read the goal, before-and-after screens, and remaining feedback. If there is no visual review, ask for screenshots or steps explaining the intended result.

Run the pull request's branch using the project's setup instructions. Follow the handoff steps, compare the app with the intended UI, and review the code. Run the project's required checks, including relevant behavior and accessibility tests.

Leave requested changes in the pull request and agree on who will make them. Confirm whether further design review is needed before following your team's merge and release process.

If handoff fails

Read the error and check repository access. Use Fix with agent if offered, then Try the handoff again once the problem is fixed. For access or branch problems, see Troubleshooting or ask your developer.