Submora01PREPARATION CHECKLIST
Know the fields before you open the form.
Prepare the information below using the saved platform configuration. Required labels reflect that configuration; confirm the current form before submitting.
01
App title
Required- Input
- Short text
- Form step
- App
02
App tagline
Required- Input
- Short text
- Form step
- App
03
Description
Optional- Input
- Long text
- Form step
- App
- Requirements
- Optional Markdown with fenced code blocks. Use only real features, build process, stack, challenges and metrics; do not invent a hackathon story.
04
App website
Required- Input
- Website URL
- Form step
- App
05
Video demo
Optional- Input
- Website URL
- Form step
- App
- Requirements
- Recommended, not required. Use an actual YouTube/Vimeo or other demo URL.
06
Your name
Required- Input
- Short text
- Form step
- App
07Email
Optional
- Input
- Email address
- Form step
- App
- Requirements
- Optional. The page says hidden and used for hackathon notifications.
08
Screenshot
Optional- Input
- Image upload
- Form step
- App
- Requirements
- Recommended. Image/* accepted; no size or dimensions stated.
- Image requirements
- Confirm file requirements on the submission form.
09
Additional images
Optional- Input
- Image upload
- Form step
- App
- Requirements
- Optional, up to four additional images. Multi-file input accepts image/*; no size or dimensions stated.
- Image requirements
- Confirm file requirements on the submission form.
10
GitHub repository
Optional- Input
- Website URL
- Form step
- App
11
LinkedIn share or profile link
Optional- Input
- Website URL
- Form step
- App
12
X share or profile link
Optional- Input
- Website URL
- Form step
- App
13
Team name
Optional- Input
- Short text
- Form step
- Team
- Requirements
- Optional hackathon-team information. Do not fill if not participating as a team.
14
Number of team members
Optional- Input
- Short text
- Form step
- Team
- Requirements
- Optional team section; numeric range one to ten. The initial one is a form default, not a verified team size.
15
Team member name
Optional- Input
- Short text
- Form step
- Team
- Requirements
- Optional repeating member details, up to ten. The observed first row uses member-name-0; fill later rows manually with actual member facts.
16
Team member email
Optional- Input
- Email address
- Form step
- Team
- Requirements
- Optional actual member contact, paired with the corresponding name. Do not copy the submitter email to every member.
17
Tags
Required- Input
- Choose multiple options
- Form step
- Tags
- Requirements
- At least one existing or newly added tag is required. Eight featured shortcuts (convex, AllGasHackathon, OpenAI, Firecrawl, codex, AgentMail, Astra, Fable) are not the full catalog. Search the live catalog; choose only actual technologies or participation tags.
18
New tag
Optional- Input
- Short text
- Form step
- Tags
- Requirements
- Optional custom factual tag, added with Add. No tag should imply an unverified technology or hackathon participation.
02PLATFORM REQUIREMENTS
Before you submit
- App title, tagline within 140 characters, actual website and submitter name
- At least one factual existing or custom tag
- Optional factual build details, real media and team participation information
Submission fees are unverified. No payment was made during verification. Check any later fee or checkout requirements before final submission.
03PUBLISHING WORKFLOW
How to submit
- 01
Open Submit your app. The form can be inspected without an account.
- 02
Enter title, factual tagline within 140 characters, website and your name. Optional Markdown description, demo, contact email and social/repository links must be real.
- 03
Optionally upload a screenshot and up to four additional images. Team Info can remain closed; if used, enter only actual team details for up to ten members.
- 04
Select or add at least one factual tag. Search the live catalog; featured hackathon and technology labels must not imply unverified participation. New tags allow 32 characters.
- 05
Review before Submit App. No deadline or appointment selector is shown, and final publication was not tested. Record the actual result and public URL.
04EXPECTED OUTPUT
What gets published
A product name, description, website link, and any product media accepted by the destination.
Not suitable for
- Products that are not live or cannot be accessed publicly
- Products that clearly fall outside the destination eligibility criteria
The destination controls pricing, moderation and publication. DR is a recorded metric, not a guarantee of traffic or acceptance.
PREPARE. PUBLISH. FOLLOW UP.
Keep the work connected.
Use your website materials to prepare platform-specific content, record your submission and follow the published result.