Review first
Use prototype and graph views to inspect the screen structure before pushing the project further.
TestFlight Upload
Move From Prototype Review to TestFlight Testing
Pixelmost supports the step from app concept and flow review into TestFlight testing, so you can validate the product on real devices instead of stopping at mockups.
If TestFlight is part of your workflow, Pixelmost helps you review structure first, prepare the project, and continue into App Store Connect and device testing.
- Review structure before device testing
- Prepare for App Store Connect
- Supports TestFlight workflows on higher plans
- AI Max includes 5 TestFlight upload tokens
Where TestFlight support fits in the Pixelmost workflow
TestFlight matters when the design is no longer only a concept. At that point you want to check flows on real devices, collect feedback, and find issues before a public release.
Prepare for App Store Connect
Make sure app metadata, bundle ID, certificates, and distribution choices are lined up before upload.
Test on devices
Move into TestFlight when the key journeys are ready to be validated outside the design review stage.
What to have ready before uploading
The smoother TestFlight step starts with basic setup already in place.
App Store Connect setup
Have the app record, team access, bundle ID, and build strategy defined before you try to ship a build.
Signing and profiles
Certificates, bundle identifiers, and provisioning profiles still need to match for uploads to work cleanly.
Clear testing goal
Know whether the first round is internal QA, a partner review, or a broader external beta group.
How the Pixelmost TestFlight upload flow works
The upload is a sequence of product review, Apple setup, build creation, and processing. Keeping those stages separate makes failures easier to diagnose.
1. Open the build flow
From the Pixelmost editor, open Share and choose Upload prototype to enter the Build and publish flow for the current app.
2. Select an organisation
Choose the Apple organisation whose credentials and App Store Connect access match the app you intend to upload.
3. Review app identity
Confirm the App Store Connect app, Bundle ID, version, and build number. The identifiers must describe the same app before signing and upload can succeed.
4. Start the build
Choose Build and publish to TestFlight. If Pixelmost asks to link the organisation to the app, confirm the relationship for later builds.
5. Wait for processing
Build and upload happen first. Apple then processes the build in App Store Connect, so it may not appear in TestFlight immediately.
6. Add testers
After processing, configure internal testers in TestFlight. External distribution follows Apple's beta review and tester setup requirements.
What Pixelmost handles and what stays in Apple's systems
Pixelmost turns the project into an installable prototype build and starts the TestFlight upload from its build flow. Apple Developer and App Store Connect still own the App ID, Bundle ID, team access, signing relationship, build processing, tester groups, and any external beta review. You need a valid Apple Developer setup plus a Pixelmost plan with build tokens; compare current plan limits before starting.
Detailed setup guide
If you are working through App Store Connect, certificates, and internal versus external testing, the guide below is the best companion to this page.
Related pages
These pages cover the steps that usually lead into TestFlight testing.
App Prototype Tool
Use Pixelmost to review screens, connections, and product flow before you move into device testing.
Graph Mode
Inspect the screen map in one view so missing routes and structural issues are easier to catch first.
Pricing and TestFlight tokens
See which plan includes TestFlight upload tokens and how the workflow fits with other Pixelmost features.