Disclosure: This guide contains affiliate links. Launchda may earn a commission if you purchase through them, at no extra cost to you. Tool choice does not affect contest eligibility or project approval.
Ready to turn the idea into a working project?
Choose the tool that fits your workflow. You never need a specific tool to use Launchda or enter the contest.
What makes an Emergent prompt useful
A useful Emergent prompt describes the person, the problem, the main workflow, the required result, and the boundaries of the first version. The tool's own prompting guidance recommends starting with the why and who, focusing on a few essential features, building incrementally, and testing before expanding.
Treat the prompts below as frameworks rather than magic commands. Replace the example audience and details with information from people you can actually reach.
- Lead with the user and their problem
- Limit the first build to two or three essential features
- Describe the inputs and expected result
- Request responsive behavior and useful error states
- State what should not be built yet
Campus operations prompts
Campus processes are strong portfolio material because you can observe the current workaround and test quickly. Start with fictional data, especially when the finished product could contain student information.
- Canteen queue: Build a mobile-friendly pre-order prototype for one campus canteen. Students view today's sample menu, choose items, receive a pickup number, and see an estimated wait. Include staff order status controls. Do not add payments in version one.
- Hostel maintenance: Build an issue reporter where residents choose a location and category, add a description and photo, then receive a tracking number. Include a sample status lookup and an admin queue. Do not require login yet.
- Club deadlines: Build a searchable board for one college department. Students browse events, competitions, and application deadlines, save items locally, and filter by category and date.
- Lab equipment: Build a simple issue log where students report faulty equipment and lab staff update its status. Include clear empty, success, and error states.
Learning and placement prompts
Do not ask an app to solve all of education or placements. Choose one repeated task and make the output easy for a student to check.
- Revision planner: Build an app where a student enters subjects, exam dates, confidence levels, and available hours. Produce a seven-day revision plan that the student can edit and mark complete.
- Viva practice: Build a practice tool for one course where students choose a topic, answer sample questions, reveal model points, and track topics that need revision. Label generated content as practice material.
- Application tracker: Build a private internship tracker with company, role, deadline, status, contact, and next action. Include filters and a weekly follow-up view.
- Peer study matcher: Build a prototype where students list subject, preferred time, campus area, and study style, then see compatible sample matches. Do not expose phone numbers publicly.
Local organisation prompts
Small organisations often have clear manual workflows that make good student projects. Ask permission before using a real organisation's name or data.
- Tutor enquiries: Build a lightweight enquiry dashboard for a tutor with student name, course interest, preferred time, status, and follow-up date.
- Volunteer shifts: Build a coordinator for a local nonprofit where volunteers view sample shifts, claim one, and see confirmation while an organiser monitors capacity.
- Shop stock reminders: Build a simple inventory reminder for a small shop. Staff add products, current quantity, and reorder level, then see a low-stock list.
- Service appointments: Build a request page for a local repair service with service type, preferred slot, area, and issue description, plus a simple staff queue.
How to iterate after the first prompt
Once Emergent produces a first version, test the main journey before requesting more features. Give one focused follow-up at a time: name the screen, the action, the expected result, and what happened instead.
Finish by testing on a phone, checking the published URL, and documenting the prompt, important corrections, user feedback, and final result in your Launchda portfolio.
- Fix blocking behavior before visual polish
- Separate feature requests from bug fixes
- Use real task-based feedback
- Keep a stable version before a large change
- Publish only after testing the public build