Seven distinct worlds. Seven different challenges. Seven opportunities to think beyond conventional software development.
Each theme presents a unique scenario with its own constraints and expectations. Your task is to choose one theme, interpret the challenge, and develop an original solution.
We won't tell you exactly what to build. That's part of the challenge.
1. Tech for a Fictional IslandYour Role: Founding Minister of Digital Infrastructure
Welcome to the Republic of Vespera, a newly independent archipelago located in the middle of the ocean.
Vespera is unlike any country you've encountered. It spans three time zones, operates an economy backed by sea salt, and experiences monsoon seasons lasting nearly half the year.
Its population is eager to embrace technology, but the nation faces significant challenges. Internet connectivity is unreliable, electricity is limited in remote regions, and traveling between islands becomes dangerous during extreme weather.
With no legacy digital infrastructure, the country has a rare opportunity to design its systems from the ground up.
The government has appointed you to help shape its digital future.
Your Mission
Identify a critical challenge facing Vespera and develop a technological solution that addresses it.
Your solution must reflect the country's unique geographical, economic, environmental, or infrastructural conditions.
Challenge Requirements
-
Identify a meaningful problem affecting the fictional nation.
-
Incorporate at least two characteristics or constraints unique to Vespera.
-
Consider how your solution behaves when infrastructure or resources are limited.
-
Demonstrate a functional implementation of your proposed system.
-
Explain the reasoning behind your technical decisions.
The Question: If you could design technology for a country starting from zero, what would you build first, and why?
2. The Reverse HackathonYour Role: Chief Innovation Officer of Terrible Ideas
Welcome to the Anti-UX Summit, where simplicity is considered a design failure and user frustration is a competitive advantage.
In this universe, software companies are celebrated for creating the most unnecessarily complicated digital experiences imaginable.
Products are judged not by how quickly users accomplish their goals, but by how creatively they obstruct them.
You've been invited to unveil the next revolutionary breakthrough in terrible user experience.
Your Mission
Create a functional digital product that deliberately violates established user experience principles.
Your challenge isn't to write broken code. It's to engineer an experience where the frustration is intentional, consistent, and creatively designed.
The application should accomplish something, but in an unnecessarily difficult or absurd way.
Challenge Requirements
-
Build a functioning application with intentionally frustrating interactions.
-
Incorporate at least three distinct violations of established UX principles.
-
Ensure frustrating behaviors are intentional rather than accidental software defects.
-
Explain the design principles you've deliberately reversed.
-
Present the product as though its terrible user experience is its greatest innovation.
Keep your experiment safe: no real financial harm, unauthorized data collection, or irreversible actions.
The Question: How badly can you design something when you understand exactly what good design looks like?
3. Grandma-ProofYour Role: Accessibility-First Product Designer
Imagine an 80-year-old person trying to use a digital service that younger generations consider effortless.
The interface is filled with symbols they've never encountered, navigation patterns they don't recognize, and terminology they've never learned.
What seems intuitive to one generation can become an obstacle to another.
Your responsibility is to eliminate that barrier.
Your Mission
Design and build a genuinely useful digital experience that an older adult can operate independently, without needing someone to explain each step.
The challenge is not simply to make buttons bigger or increase font sizes. You must understand how users with different levels of digital familiarity approach technology.
Challenge Requirements
-
Address a genuine everyday need.
-
Make the primary task understandable without written instructions or external assistance.
-
Prioritize clarity, accessibility, readability, and predictable interactions.
-
Conduct at least one usability testing session with a real older adult.
-
Document observations from the testing session and demonstrate how feedback influenced your design.
Obtain the participant's consent, and avoid collecting unnecessary personal information.
The Question: Can you build something so intuitive that someone unfamiliar with modern interfaces understands how to use it?
4. Alien OnboardingYour Role: Earth's First Interstellar Experience Designer
An extraterrestrial delegation has just landed in Dhaka.
They possess advanced intelligence and technology, but they know absolutely nothing about human civilization.
Everyday behaviors appear irrational to them. Social customs seem mysterious, familiar symbols have no meaning, and concepts humans take for granted require entirely new explanations.
The visitors need a way to understand Earth before returning to their homeworld.
You've been selected to design their onboarding experience.
Your Mission
Choose a complex aspect of everyday human life and create an interactive experience that explains it from the ground up.
Assume your audience has no prior familiarity with the subject. Every concept, relationship, and convention must be introduced thoughtfully.
Your solution should help users understand not just what humans do, but why they do it.
Challenge Requirements
-
Focus on one clearly defined aspect of human society or everyday life.
-
Build an interactive experience rather than relying entirely on static explanations.
-
Introduce concepts progressively without assuming background knowledge.
-
Use storytelling, visual communication, or interactive learning to develop understanding.
-
Demonstrate how someone unfamiliar with the subject can learn from your experience.
The Question: How would you explain something completely ordinary to someone who has never encountered it before?
5. Ghost Town RescueYour Role: Emergency Software Recovery Engineer
A decade ago, the fictional town of Oakhaven began an ambitious digital transformation.
Public services were being modernized, government records were moving online, and residents were promised a more connected future.
Then the town's only IT contractor vanished.
The remaining software was left incomplete, undocumented, and increasingly unstable. Years of neglect have turned once-promising systems into a collection of failing applications.
Now, with essential digital services barely functioning, the mayor has called for emergency assistance.
You've been hired to investigate the damage and restore what can be saved.
Your Mission
Work with an existing, intentionally broken codebase and recover its essential functionality.
This challenge is about understanding unfamiliar software, identifying root causes, and making thoughtful repairs—not simply replacing everything with a new application.
Challenge Requirements
-
Begin with the legacy repository supplied by the organizers.
-
Investigate and document the significant defects you discover.
-
Restore the system's essential functionality.
-
Improve reliability and maintainability while preserving the project's intended purpose.
-
Provide evidence that your repairs work through testing or reproducible demonstrations.
-
Explain your debugging process and technical decisions.
The Question: Can you understand and rescue software you didn't write, without knowing why it originally failed?
6. City as a GameYour Role: Real-World Experience Architect
Imagine discovering that the streets you walk every day are part of something bigger.
A familiar building might hold a hidden clue. A public square could become the center of an adventure. A location you've passed hundreds of times might suddenly have a completely different meaning.
Your surroundings are no longer just physical spaces.
They're part of an interactive world.
Your Mission
Transform an actual physical environment into an engaging, playable digital experience.
Your project must establish a meaningful relationship between where participants are in the real world and what happens within the experience.
The goal is to encourage exploration, discovery, and interaction with the surrounding environment.
Challenge Requirements
-
Base your experience around a real, identifiable physical environment.
-
Integrate at least one technology that connects physical locations or objects with digital interactions.
-
Establish clear objectives, progression, or completion conditions.
-
Ensure real-world participation meaningfully influences the experience.
-
Demonstrate the interaction between physical movement or discovery and the digital system.
Design the experience responsibly. Do not require trespassing, unsafe movement, or access to restricted locations.
The Question: Can you transform an ordinary place into an experience people want to explore?
7. Smallest Possible Product (SPP)Your Role: Product Craftsmanship Engineer
Modern software development often rewards adding more.
More features. More pages. More integrations. More complexity.
But what happens when you're forbidden from expanding your product?
Imagine being allowed to build only one feature on one screen.
You can't solve problems by introducing more interfaces or additional functionality. Every improvement must come from making the existing experience better.
That's your challenge.
Your Mission
Build a digital product with exactly one primary feature and one screen.
Focus on making that single capability exceptionally reliable, accessible, performant, and enjoyable to use.
Every interaction, visual decision, error state, and performance improvement should serve the product's one purpose.
Challenge Requirements
-
Implement exactly one primary feature on one screen.
-
Avoid secondary pages, unrelated settings, and unnecessary functionality.
-
Prioritize usability, accessibility, performance, and edge-case handling.
-
Demonstrate meaningful refinement of the product through iteration.
-
Explain the technical and design decisions that improve the experience.
Additional features do not earn extra credit. Unnecessary complexity may count against your submission.
The Question: How close to perfection can you take a single feature when adding more is no longer an option?
General Participation GuidelinesChoose One Arena
Every participant must select one theme. Your submission should clearly demonstrate how your project addresses its central challenge.
Interpret the Challenge Creatively
The scenarios define the problems and constraints, not the solutions. You're encouraged to explore unconventional approaches and develop your own ideas.
Build Solo
All projects must be developed independently. Participants are responsible for their own architecture, design, implementation, testing, and presentation.
Show What Works
Submissions should demonstrate a functional implementation rather than just presenting a concept or design proposal.
Document Your Thinking
Explain the problem you chose, your approach, the challenges you encountered, and the decisions you made along the way.
Your Arena. Your Interpretation.There is no single correct solution to any of these challenges.
Two participants choosing the same theme might develop completely different projects, and that's exactly what we want.
We're looking for independent thinking, creative interpretation, and thoughtful execution.
Choose your arena. Define your challenge. Build your solution.
Requirements
To qualify for judging, all participants must submit their projects through Devpost before the submission deadline.
Your submission should clearly demonstrate what you built, how it works, and how it addresses your chosen theme.
1. Working Project-
Build a functional project based on one of the seven hackathon themes.
-
Your project must be developed individually. Team submissions are not allowed.
-
You are free to use any programming language, framework, or technology stack.
-
Your submission must demonstrate meaningful functionality. Concept-only submissions, mockups, or presentation slides without a working implementation are not sufficient.
-
AI development tools, open-source libraries, and third-party APIs are permitted. Any external resources used must be properly acknowledged.
Your Devpost submission must include:
-
Project Name: A clear and creative name for your project.
-
Selected Theme: Specify which of the seven themes you chose.
-
Project Overview: Briefly explain what your project does.
-
Problem & Approach: Describe the challenge you addressed and why you chose your solution.
-
Technical Implementation: Explain the technologies, architecture, and important technical decisions.
-
Challenges & Learnings: Share the obstacles you encountered, how you approached them, and what you learned.
Provide a link to your project's source code repository (GitHub, GitLab, or equivalent).
Your repository should include:
-
A README explaining the project and how to run it.
-
Clear setup and installation instructions.
-
Any necessary configuration details or sample environment variables (without exposing secrets).
-
Appropriate acknowledgment of third-party code, libraries, assets, and other resources.
For the Ghost Town Rescue theme, participants must also document the original issues, the changes they made, and how they verified their fixes.
4. Project Demonstration VideoSubmit a 2–5 minute demonstration video showing your project in action.
Your video should cover:
-
Your selected theme and the problem you're addressing.
-
A walkthrough of your project's primary functionality.
-
How your solution satisfies the chosen theme's requirements.
-
Any particularly interesting technical or creative decisions.
A screen recording with voice narration is sufficient. Professional video editing is not required.
Upload your video to YouTube, Vimeo, or another accessible platform and include the link in your Devpost submission.
5. Live Demo (Recommended but optional)If applicable, provide a publicly accessible link to your deployed application or interactive demo.
A live deployment is encouraged but not mandatory, particularly for projects involving local systems, hardware, or location-dependent experiences.
If a live demonstration isn't feasible, ensure your video and documentation clearly show the project functioning.
6. Theme-Specific EvidenceSome themes have additional requirements. Include the relevant evidence in your Devpost description or repository.
| Theme | Additional Requirement |
|---|---|
| Tech for a Fictional Island | Explain how your solution addresses at least two of Vespera's unique constraints. |
| The Reverse Hackathon | Identify at least three deliberately violated UX principles and demonstrate them. |
| Grandma-Proof | Provide evidence of usability testing with an older adult, including observations and improvements made. |
| Alien Onboarding | Demonstrate the interactive learning experience and its progression from basic concepts. |
| Ghost Town Rescue | Document the defects discovered, repairs made, and testing or verification results. |
| City as a Game | Demonstrate the connection between real-world locations or objects and your digital experience. |
| Smallest Possible Product | Demonstrate adherence to the one-feature, one-screen constraint and explain the refinements made. |
For usability testing, do not publish participants' faces, names, recordings, or other personal information without their explicit consent.
7. Submission ChecklistBefore submitting, make sure you have:
-
Selected exactly one hackathon theme.
-
Built a functional project that meets the selected theme's requirements.
-
Completed your Devpost project description.
-
Added a source code repository with a README.
-
Included a 2–5 minute demonstration video.
-
Provided theme-specific evidence, where required.
-
Added a live demo link, if available.
-
Acknowledged any AI tools, third-party code, or external resources used.
Important: Judges should be able to understand and evaluate your project using the materials you submit. Make sure your links are accessible and your documentation is clear.
Prizes
TBA
Prize will be given to users. It will announced soon
Judges
TBA
Judging Criteria
-
Creativity & Originality
How original, imaginative, and thoughtful is the project's approach? Judges will evaluate creative interpretation of the selected theme, uniqueness of the concept, and the participant's ability to think beyond conventional solutions. -
Technical Execution
Evaluates functionality, reliability, code quality, and technical decisions. Rewards thoughtful implementation and engineering quality over unnecessary complexity. -
Theme Alignment & Problem-Solving
Evaluates how effectively the project addresses its chosen theme, follows its constraints, and demonstrates meaningful problem-solving. -
User Experience & Craftsmanship
Evaluates design quality, usability, accessibility, and attention to detail in the context of the chosen theme, including intentionally unconventional experiences.
Questions? Email the hackathon manager