Archestra Apps HackathonSee what people are building

Thread

S
stephdai2862:47 AMOpen in Slack
Hi! I’m getting ready to submit my Apps Hackathon project and wanted to clarify the video requirements.
For the submission recording, are we expected to show the full app-building process from the original prompt onward, or is it enough to show the final prompt, a few key chat iterations, and then demo the completed app? Do judges need to see the chat logs or exact prompts used?
Is there a recommended video length or maximum duration? Also, should the video include narration, or is a silent screen recording with the app flow acceptable?
A few other questions:
• Should the recording focus mostly on the final app experience, or also explain how the MCP server and live data integration work?
• Do we need to show the submission PR creation process in the recording?
• Are there any specific items that must be visible, such as the MCP servers used, the live-data state, or the generated app prompt?
• How heavily is UI/UX and visual polish weighted compared with technical complexity, usefulness, and depth of MCP integration?
Thank you! I just want to make sure I record and submit everything correctly.

3 replies
A
Archestra2:48 AMOpen in Slack
Great questions! Let me check the official hackathon docs for the exact requirements. I can't fetch the docs directly right now, but here's what I know from the hackathon page: *Video: Show the final app in action + briefly highlight the MCP integration. No need to record the entire build process or PR creation. A few minutes is plenty — keep it concise. Format: Narration is nice but not required. Silent screen recording with clear flow works fine. What to show: - The working app demo (main focus) - Which MCP server(s) you used and how live data flows through - The prompt/chat that generated it is helpful context but not mandatory to show in full Judging: Per the hackathon page, they weigh creativity, usefulness, and MCP integration depth. Visual polish matters but isn't the primary focus — a functional, clever use of MCP tools beats a pretty but shallow app. PR:* Just submit it per the instructions; no need to record that process. TL;DR: Demo the app, highlight the MCP magic, keep it short. Good luck! 🚀 🤖 Slack Agent
S
stephdai2865:06 AMOpen in Slack
what size/dimension should the final app be? 900x1000 or more like a mobile app or website dimension
A
Archestra5:06 AMOpen in Slack
App dimensions are flexible — there's no required size. The canvas defaults to 900px wide but you can adjust it. Pick whatever fits your app best: - *Dashboard/data-heavy: wider (900–1200px) - Mobile-style:* narrower (400px) - *Tool/utility:* whatever feels natural Judges care about the experience, not specific dimensions! 🤖 Slack Agent