How to Collaborate with Other Game Developers on iPad
You can collaborate with other game developers on a hyperPad game by splitting the work into clear roles, agreeing on how files and Projects move between you, and testing each other's builds with a specific question. One person might own the Behaviors, another the art, and another the music. The game comes together when everyone knows what they're making and where it goes.
This guide covers how to find collaborators, divide the work, share assets and Projects, and give feedback that helps.
Find people to build with
Start where creators already talk about hyperPad.
- The hyperPad Discord is a good place to ask focused questions about Projects and Behaviors, and to meet creators who want to team up.
- The hyperPad Hub shows what other creators have made. If someone's art style or game feel matches what you have in mind, that's a good person to reach out to.
- Friends, classmates, and local game clubs work too. A collaborator doesn't need to know hyperPad to draw Graphics or write music for your game.
Hub access is limited to creators age 13 or older, and creators ages 13 to 17 need parent or guardian permission under the current Terms of Service.
Agree on the game before you split the work
Write the game in one sentence that everyone agrees on:
The player drags a magnet to pull coins out of a cave before the lights go out.
That sentence tells the artist what to draw, the musician what mood to aim for, and the builder which mechanic to make first. If the team can't agree on the sentence, you'll end up with assets that don't fit together.
Then list the first playable Scene and nothing more. One player Object, one hazard, one goal, a score Label, and a restart button is enough for a team's first milestone.
Divide the work by role
| Role | Owns | Hands over |
|---|---|---|
| Builder | The hyperPad Project: Scenes, Objects, Attributes, and Behaviors | Playable builds to test |
| Artist | Graphics, animation frames, and interface art | Transparent PNG files at an agreed size |
| Audio | Music loops and sound effects | Trimmed audio files named by game event |
| Tester | Play sessions and notes | One clear problem per build |
On a small team, one person often holds two roles. Keep one person responsible for the Project itself, so changes don't overwrite each other.
Share assets in a format everyone can use
Agree on the rules before anyone makes final files:
- one pixel size or grid for characters and tiles
- transparent PNG for Graphics
- the same canvas size for every frame of an animation
- file names that describe the game role, like
player_run_01.pngorsfx_coin.wav - one shared folder in iCloud Drive, Dropbox, or another service the Files app can open
The builder imports the files through the Asset Library. The Importing Assets guide covers the sources hyperPad can import from, and Supported Asset Types lists the formats to export.
Keep the source of every third-party file, its creator, and its license in the same shared folder. Everyone on the team should know what you're allowed to Publish.
Build on each other's work with Branch
When a creator Publishes a Project to the Hub as Open Source, anyone can Branch it. Branching gives you your own copy of the Project to explore and change. Closed Source Projects can't be branched.
Branching is useful for collaboration in two ways. You can study how another creator organized Objects and Behaviors for a mechanic you want to learn. And a teammate can Publish a small test Project as Open Source so others can branch it and try a fix in their own copy.
Credit the original creator when your game builds on their Project, and check their notes before you reuse their art or audio.
Test each other's builds with one question
Feedback between collaborators works best when it's specific. Before you hand over a build, choose one question:
- Does the player understand the goal without an explanation?
- Can the player jump on the first try?
- Does the coin sound play at the right moment?
Give the tester the goal, then watch without explaining. Write down what happens: "Tapped the character instead of the jump button" is useful. "The controls are confusing" is a guess about why.
Sort each note as a bug (the game breaks a rule you designed), a clarity problem (it works, but the player can't tell what to do), or a preference (they'd like a different color or genre). Fix bugs first, then clarity problems. Treat preferences as one opinion.
Ask for help from the wider community
When you're stuck, a clear request gets better answers. Include what you're building, what you expected, what happened, and what you already tried. For example:
I'm building a one-screen platformer. The jump should only work while the player is touching the ground, but it sometimes triggers in mid-air. I checked the ground collision and the If Behavior. Which value should I display while testing the grounded state?
That gives another creator a concrete problem to look at. The Behavior Editor overview helps when you need to trace the logic behind a bug yourself.
Keep a shared log
A short log keeps the team in sync. One line per change is enough:
| Date | Who | Change | Result |
|---|---|---|---|
| Week 1 | Artist | Made the jump button larger | New tester jumped on the first try |
| Week 1 | Builder | Added "Exit open" Label after five coins | Players walked to the door without help |
Change one thing per build. If the team changes the button, the level layout, and the speed at once, nobody will know which change helped.
Start with one shared Scene
Pick one teammate, agree on the one-sentence game, and build a single playable Scene together this week. For a small game to practice on, follow How to Make a Game on iPad for Free, then swap roles for the next Scene.
