The submission form is behind a login, but based on RevenueCat's official guidelines + standard Devpost structure, here's what they're asking for:
Basic Info:
- Project Name - "Quest Planner"
- Tagline (short, catchy) - "Turn your dreams into daily micro-actions"
- Which Creator Brief? - Dropdown: Select "Gabby Beckford (@packslight)"
Assets:
- Demo Video URL (required) - YouTube/Vimeo link, 2-3 min max
- Images/Screenshots - 3-5 key screens (Campaign Select, Briefing, Home, Quest Detail, Stamp Collection)
- TestFlight Link (required for iOS) - Public link, no email required
Technical:
- Built With (tags) - React Native, Expo, RevenueCat, AsyncStorage
- GitHub/Code Repository (optional, but recommended)
Based on their requirements doc, expect these:
1. Project Description / "Here's the whole story" (This is the big text box - likely has guidance headers)
Expected sections:
- Problem Statement - What problem does this solve for [Creator]'s audience?
- Solution Overview - How does your app solve it?
- Target Audience - Who is this for? (Gabby's audience: adventurous women seeking life upgrades)
- Key Features - What makes it special?
2. Monetization Strategy
- How did you integrate RevenueCat?
- What's your pricing model? (Free vs Premium)
- What's behind the paywall?
- What's your rationale for pricing?
3. Technical Documentation
- Architecture overview (React Native, Context API, AsyncStorage, etc.)
- RevenueCat integration details (how you use SDK, entitlements, offerings)
- Any technical challenges you solved
4. Developer Bio
- Your background
- Why you built this
- Portfolio/previous work links
- What excites you about this project
5. Future Roadmap (Post-Hackathon Plans)
- What's next for the app?
- Additional campaigns planned?
- Community features?
- Creator partnerships?
- Inspiration - What inspired you to build this?
- What it does - One-sentence summary
- How we built it - Tech stack details
- Challenges we ran into - What was hard?
- Accomplishments we're proud of - What worked well?
- What we learned - Key takeaways
- What's next - Future features
(These are standard Devpost prompts, not sure if RevenueCat uses all of them)
Based on your hackathon-submission-plan.md:
✅ TestFlight Link - Public external testing link ✅ Demo Video URL - 2-3 min, uploaded to YouTube unlisted ✅ Screenshots - 3-5 images from key screens 📝 Written Proposal - 1-2 pages covering problem/solution/monetization/roadmap 📝 Technical Docs - Architecture + RevenueCat integration details 📝 Developer Bio - Your story, why this project
- Tagline: ~50-80 chars
- Description: Usually 5000-10000 chars (about 1-2 pages)
- Each section: 1000-2000 chars
- Use the description sections as your "written proposal" - Don't write separately, just fill the form
- Screenshots matter - Judges see these before watching video
- Tagline should mention Gabby - "Built for Gabby Beckford's audience" or similar
- Built With tags - Include "RevenueCat" so they can filter/find it
Pre-fill a Google Doc with:
- Problem statement (200 words)
- Solution overview (300 words)
- Monetization strategy (200 words)
- Technical architecture (300 words)
- Developer bio (150 words)
- Roadmap (150 words)
Then copy/paste into Devpost form sections. Easier to edit/review before submitting.
Want me to draft any of these sections based on your current Quest Planner app?
Sources: