Submitting your app to Shipyard should be straightforward, as you don’t need to navigate app store reviews or production release requirements to participate. What matters is that judges can install and evaluate your app reliably during the hackathon.
This article explains exactly what is required, what is optional, and how to submit your app correctly.
Shipyard rule recap
Before you submit your app, make sure your app adheres to the rules of Shipyard:
- Mobile apps only — iOS, Android, or cross-platform (no web/desktop apps)
- All projects must be started and completed within the hackathon timeframe
- Participants can only submit one app for one brief — choose wisely!
- RevenueCat integration is mandatory — subscriptions or in-app purchases
- Apps must be on TestFlight (iOS) or Play Internal Testing (Android) — you can have the app live on app stores, but this isn’t required
- Developers retain full ownership of all intellectual property
- If you use an influencer’s name or likeness, you must remove it before public launch (unless agreed with the influencer)
- Any post-hackathon collaboration with influencers is separate from RevenueCat
Let’s take a closer look at a few key rules next.
What can you build your app with?
The main goal of Shipyard: Creator Contest is to build an MVP of a mobile app for the selected creators’ audience. You can use any technology (Swift, Kotlin, Flutter, React Native, etc.) or tool (Cursor, Xcode, Claude, Vibecode, Rork, etc.), as long as it produces a mobile app that can be uploaded to either Apple App Store or Google Play Store. This means that web apps are out of the scope of this hackathon. Tools such as Capacitor are allowed, in case you’re turning a web app into a native mobile app.
Your app must have RevenueCat integrated
Your app must have a version of the RevenueCat SDK installed on it, and you must have your in-app purchases configured for the platforms your app is targeting, and the in-app purchase products need to be purchasable. Test store configuration is not counted as an integrated SDK.
Full configuration of RevenueCat requires you to have either an Apple Developer account or Google Play developer account.
- Your app must have RevenueCat SDK integrated
- App must have subscriptions and/or in-app purchases
- Test store integration is not enough
Apps must be on TestFlight (iOS) or a Google Play testing track (Android)
Your app must be distributable through either TestFlight in App Store Connect, for iOS apps; or Google Play Public/Closed/Internal testing track, for Android apps. This means that you need to have an account on at least one of those stores for the app you’re submitting. Sadly RevenueCat is unable to cover the cost of the developer account for participants.
For TestFlight distribution, at least one app has to have been submitted to App Store Connect, and made available for distribution on the TestFlight tab. The app you submit to Shipyard should have External testing enabled, with a public link. Attach the public link to your Devpost submission.
For Google Play Console testing tracks, your app has to be uploaded to Google Play Console and made available through an Internal, Closed, or Public testing track so judges can install and evaluate it.
You CAN publish your app (but it’s optional)
Making your app public and publishing for people to download from the App Store and Google Play Store is allowed during and after the hackathon. Doing this will not affect judging, but you’re also not required to wait on publishing your app.
- Publishing during Shipyard is allowed
- Publishing does not disqualify your app
- Publishing does not affect judging
How to submit your app to Shipyard
Your app needs to be testable on either iOS or Android devices, with distribution done either through TestFlight for iOS, or one of Google Play Console testing tracks for Android.