US Freelancer Needed: Capture End-to-End Zocdoc GP Appointment Booking UX (Desktop + Mobile)

Title US Freelancer Needed: Capture End-to-End Zocdoc GP Appointment Booking UX (Desktop + Mobile Screenshots) IMPORTANT: Must have access to medical insurance (Medicare accepted) Description We are building a Mobbin-style UX/UI flow library focused exclusively on healthcare and healthtech platforms. Use https://www.healthtechremix.com/ and https://mobbin.com/ for reference. We are looking for a US-based user who can register, book, and complete a real GP (General Practitioner) appointment on Zocdoc (https://www.zocdoc.com/) and capture pixel-accurate, full-page screenshots of the entire end-to-end user journey, for both desktop and mobile views. This is paid UX research work. We will cover any appointment booking fees upfront. This is the first of many similar projects, so we are ideally looking for someone we can work with long-term. What You Will Do You will capture the complete end-to-end Zocdoc experience, including: Priority Flows New user registration / sign-up Returning user login GP search and filtering GP/clinic profile viewing Insurance verification and entry Appointment booking (select date/time) Payment/insurance confirmation Booking confirmation and post-booking screens Appointment reminders (email/SMS if triggered) GP Appointment Follow-up or post-appointment screens Appointment cancellation/rescheduling flows (if accessible) Intentional error states, such as: Invalid or missing fields Incorrect information entry Unavailable appointment slots Insurance verification failures Payment processing errors Blocked or unsupported actions Any other errors you can trigger during the flow All flows must be captured from start to finish, including: Dropdowns or option menus Modals, pop-ups, and overlays Confirmation screens System messages and alerts Search filters and sorting options Insurance selection/verification screens Payment information screens Any friction or blockers Capturing Error States (Mandatory) To ensure all error states are captured, you must actively attempt to trigger them by: Entering invalid information (phone numbers, emails, incorrect formats) Skipping required fields and attempting to submit Searching with impossible filters to see empty states Attempting to book with missing or incorrect insurance information Testing payment scenarios with invalid data Any other edge cases or error scenarios you can identify You must capture: Field-level validation messages Page-level or banner errors Disabled button states (if present) Empty state designs Payment/insurance rejection messages Any system errors or warning messages Error states are considered part of the core UX flow and must be documented with the same screenshot standards as the main journey. You can find a real-time example video of the screenshot capturing process here: https://www.loom.com/share/42d3e8bb1ff74c8ab6c233bcdf217ff0 App Continuation & Screen Stitching (Critical) Some Zocdoc journeys may begin on the desktop website but require the user to continue or complete the process in the mobile app. If this happens, you must: Continue the flow in the native Zocdoc mobile app Capture all screens required to represent the full page Stitch those screenshots into a single full-page image so that it visually matches our standard full-page screenshots This stitched image will be used as the mobile source of truth and later adapted into desktop reference views on our side. Stitching Requirements Screens must be stitched with 100% accuracy No overlaps, missing UI, or misaligned elements Final output must look like a true full-page scroll capture Recommended stitching tools: https://stitchgram.com/ (web-based, free) Tailor (iOS) - https://apps.apple.com/us/app/tailor-screenshot-stitching/id926653095 Final output requirements: PNG format Sequential naming (1.png, 2.png, etc.) Correct folder structure Example stitching video: https://www.loom.com/share/0f0a2eeab3e24644843a7eec8d08f5fc Screenshot & Technical Requirements (VERY IMPORTANT) We use these screenshots in a professional UX reference database, so accuracy and consistency are critical. Devices & Capture Method Chrome DevTools Responsive Mode on a laptop/desktop computer [Shift+Cmd+C] Full-page screenshots (highest resolution possible) [Shift+Cmd+P] Mobile Viewport: iPhone standard size (XR in DevTools) Desktop: Highest available resolution full-page capture Example video: https://www.loom.com/share/42d3e8bb1ff74c8ab6c233bcdf217ff0?t=30 File Format PNG only No compression Full-page stitched images for scrollable content Folder Structure (Must Match Exactly) [Zocdoc] - [Flow Name] - [Subflow Name] - [Mobile/Desktop] - 1.png, 2.png, 3.png, etc. Examples: Zocdoc - Onboarding - Account Registration - Desktop - 1.png Zocdoc - Onboarding - Account Registration - Mobile - 1.png Each folder must represent a clear flow step. Each screenshot must be numbered in exact sequence. Example video: https://www.loom.com/share/42d3e8bb1ff74c8ab6c233bcdf217ff0?t=671 Personal Data & Privacy Because Zocdoc requires personal details: You will need to use your own real data to register and book. You must blur or redact all personally identifiable information (PII) before delivery: Name Email address Phone number Date of birth Address Insurance information (member ID, policy numbers) Medical history (if visible) Any other personal identifiers Example video of acceptable redaction quality: https://www.loom.com/share/d58d3307188a4363aefc45370207eabf Free redaction tool: GIMP (https://www.gimp.org/) Alternatively: If you are comfortable sharing unredacted screenshots privately, we can redact them ourselves (not required). This will be reflected in the job payment. Usage of Data Screenshots will be used in a public UX research platform All Personal Identifier Information will be fully removed Content is used only for design and product research, not medical purposes You must confirm: You consent to using your own data for this research task You understand screenshots will be publicly displayed once fully anonymized Final Deliverable Example This video showcases how your deliverables will be presented in our frontend. Please use this as a reference: https://www.loom.com/share/2aa6919bcbb64a2f94dc433a8a0b2f01 Access the website here: https://www.healthtechremix.com/ (NOTE: Upon signing up, you might need to check your Spam email folder to get your magic link to log in) Appointment Costs We will cover any GP appointment booking or cancellation fees upfront. Please confirm any costs with us before proceeding with the appointment. Who We're Looking For Must be US-based (able to access Zocdoc and book US GP appointments) New to Zocdoc ideally (fresh perspective on the platform) Individual freelancers only (no agencies) Strong attention to detail - every single step must be captured Comfortable following strict screenshot and file standards provided in this brief Able to deliver clean, professional full-page screenshots Nice to have: UX, product, QA, or usability testing background Previous UX documentation or testing work Experience with healthcare or telemedicine platforms Ongoing Work Opportunity This is the first of many healthcare platforms we are mapping. If this project goes well, we will offer: Ongoing similar projects Consistent paid research work Long-term collaboration Budget & Timeline Fixed Price: $250 USD Timeline: To be discussed and confirmed with selected freelancer Deliverable Checklist ✅ All onboarding and registration flows captured (mobile + desktop) ✅ Complete doctor search and selection flows ✅ Insurance verification and entry ✅ Full appointment booking flow (date, time, confirmation, video appointment) ✅ Post-booking screens and confirmations ✅ Appointment reminders (if triggered) ✅ Cancellation/rescheduling flows ✅ All error states and edge cases documented ✅ Correct folder structure and file naming ✅ All PII redacted ✅ PNG format, no compression ✅ Numbered sequentially To Apply, Please Answer: Are you US-based and able to register and book GP appointments on Zocdoc? Are you new to Zocdoc (ideally), or have you used it before? Have you done structured screenshot or UX documentation work before? (examples welcome) What device(s) will you use for mobile screenshots? Are you comfortable redacting your own personal information before delivery? Are you interested in ongoing similar UX research projects? Do you have any questions about the scope or requirements before applying? Questions? Ask before starting. We're happy to clarify scope and ensure we're aligned on deliverables.