Skip to content
AppDues
Log in
Contact salesSign up

Pitching Your App for a Hackathon: A Story-Led Demo and Devpost Guide

Judges may review dozens of submissions in a row, and a working app alone rarely survives the scroll. What makes a pitch stick is a clear problem, a visible demonstration on the target device, and a transformation the reader or viewer can picture. This guide adapts a screenwriting structure — Dan Harmon's Story Circle — to the two artifacts a hackathon submission usually needs: a short demo video and a written description.

Submission basics you cannot skip

Settle the hard requirements before spending time on narrative polish. Under the Shipaton submission rules, a valid entry includes a clear written description of the app's features and functionality; a demonstration video no longer than three minutes, which judges are required to watch; footage that shows the app working on the target device; a link to the video hosted on a public platform such as YouTube or Vimeo; and no copyrighted music, trademarks, or other protected material unless you hold the rights to use it. These are pass/fail conditions — a strong story will not make up for a missing device demo or a link that is not public. Because event rules can change, check the current wording against the confirmed rules version and video length limit before you submit.

Why a feature list is forgettable

A submission is a pitch, not an inventory. Feature lists describe what exists; stories show why it matters to someone. Judges and users rarely remember that an app has a chart — they remember that a person finally saw progress, stayed motivated, or reached a goal. The Story Circle is useful here because it is more concrete and repeatable than the broad Hero's Journey: a character leaves comfort, adapts, pays a price, returns, and is changed.

The eight Story Circle beats

Dan Harmon, the screenwriter behind shows like Community and Rick and Morty, developed the Story Circle because he wanted a model he could reuse episode after episode for episodic television. Refining the Hero's Journey gave him a simpler, more formulaic structure that still carries the emotional weight of a full story. The eight beats are: Setup (a character is in a zone of comfort or familiarity), Need (they desire something), Go (they enter an unfamiliar situation), Search (they adapt to that situation), Find (they get what they wanted), Take (they pay a price for it), Return (they come back to their familiar situation), and Change (they are transformed as a result of the journey). The movement from order into chaos and back again is what gives even a simple product pitch emotional weight.

A worked example: from feature list to story

Take a deliberately plain fitness app. Its feature-list pitch reads: personalized workout plans, progress tracking, reminders, workout logging, charts, and notifications for users of all fitness levels. Nothing in that sentence is wrong, but nothing in it explains why anyone should care. Now run the same app through the eight beats as a planning sheet. Setup: a protagonist with a packed schedule and competing family demands keeps falling off her workout routine. Need: she values fitness, yet the gym feels unwelcoming and her progress is hard to see. Go: she installs the app and treats it as a coach in her pocket. Search: tailored plans, live tracking, and nudges let her assemble a routine that survives her actual week. Find: logging a session and marking a small win becomes easy enough to repeat. Take: some mornings still resist, and steady charts plus encouraging reminders carry her through them. Return: workouts at home or at the gym become something she anticipates rather than dreads. Change: she ends up stronger and more self-assured, and the pitch closes by inviting the viewer to start the same journey. The example is generic on purpose, because the app is generic. Your job is to swap in whatever makes your project specific — a surprising use case, a quirky origin, or an unexpected benefit — since distinct stories are the ones that survive a judging queue.

Structuring the three-minute video

A strong hackathon demo leads with proof and treats polish as secondary. Open the first 15–20 seconds on Setup and Need together: name who you built for and the friction they face, using one or two moments a viewer will recognize instantly. Then move into Go and Search by showing the app running on the actual device — simple screen captures or over-the-shoulder shots that clearly demonstrate taps and responses are enough. Focus your narration on what the user is achieving, not just what the interface looks like. In the middle, highlight Find and Take: the progress being made, the effort required, and why your solution works better than alternatives; if you have numbers such as retention, completion, or time saved, show them with a quick before-and-after. Close on Return and Change: show the new normal and wrap with a one-line transformation plus a clear call to action. Keep pacing tight — judges are only required to watch three minutes, so deliver your hook and proof in the first 60–90 seconds.

Turning the video into a Devpost description

The written submission can follow the same eight beats, compressed into a few short blocks. Screenwriters use the term logline for a single sentence that captures a plot; for an app, that sentence should carry Setup, Need, and Change together. A fill-in pattern you can adapt: For [who], [App Name] helps [job to be done] by [distinct approach], so they can [valuable outcome]. After the logline, write two brief paragraphs. The first states the problem and explains where existing options fall short (Need). The second describes how the app works and what sets it apart (Go → Search → Find), staying user-centric — describe flows and outcomes rather than a bare feature inventory. Finish with a paragraph of evidence (Take → Return → Change): traction, test results, or signals from early users. Once the hook is in place, a full feature list can follow, and you can also narrate how the app came to be built; the Story Circle can shape that account too.

Pre-publish compliance checklist

Work through this list before you submit. The description explains the app's functionality clearly. The video link is publicly accessible. The demo footage shows the app working on the target device. No copyrighted assets appear without permission. The video stays within the event's confirmed length limit. The hook and the proof both land within the first 60–90 seconds. The written description opens with a logline and continues with problem, approach, and evidence paragraphs. Verify the current rule wording against the confirmed rules version for the event.

Feature list versus story: how to tell which one you wrote

A feature-list pitch names capabilities without a person: "provides personalized plans, progress tracking, and reminders." A story-led pitch names a person, a frustration, and a change: someone who could not stay consistent now looks forward to the routine. If your draft can be read without knowing who benefits, it is still a feature list. Rewrite the opening until a specific person and a specific frustration appear, then let the features enter as the tools that person uses.

Frequently asked questions

How long should the demo video be?

The Shipaton rule sets a three-minute cap, since judges are only required to watch three minutes. Put your hook and proof inside the first 60–90 seconds so the strongest material is seen even if attention drops. Check the current limit against the confirmed video length limit before submitting.

Does the video need to show the app on a real device?

Yes. The rule requires the footage to show the app working on the target device. Simple screen captures or over-the-shoulder shots that clearly demonstrate taps and responses are acceptable.

Where should I host the video?

Upload it to a public platform such as YouTube or Vimeo and include the link in your submission. The rule asks for a public platform upload plus the link in the submission.

Can I use background music?

Only if you hold the rights. The Shipaton rules prohibit copyrighted music, trademarks, or other protected material unless you have permission to use them. Check the current wording against the confirmed rules version for the event.

What is a logline and why does it matter?

A logline is a one-sentence summary of the plot, borrowed from screenwriting. For an app pitch, it compresses Setup, Need, and Change into a single sentence that gives judges the whole arc before they read the details.

Why use the Story Circle instead of the Hero's Journey?

The Hero's Journey is powerful but abstract, which makes it hard to apply directly to a product pitch. The Story Circle is more structured and repeatable: eight concrete beats that still carry the emotional weight of a full story.