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.
Prepare a one-page product brief
Do not begin with a vague prompt such as build me a student app. Write a short brief that gives Emergent enough context to make sensible product decisions.
Your brief should name the user, current problem, desired result, required screens, stored information, visual direction, and what version one must not include.
- User: second-year students in one department
- Problem: internship deadlines are scattered
- Result: one searchable list with saved opportunities
- Screens: browse, details, saved list, simple admin form
- Not included: messaging, payments, recommendations
Ask for a plan before complexity
Start by asking the builder to restate the problem and propose the smallest architecture. Check whether the plan solves the right task before authorising a large build.
Correct misunderstandings early. If the plan adds social feeds, complicated roles, or unnecessary AI features, remove them. Smaller scope creates more time for testing and improvement.
- Confirm the primary user journey
- Review the proposed pages
- Check what information will be saved
- Ask how errors and empty states will appear
- Require a responsive phone layout
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.
Build and verify one workflow
Generate the first version, then ignore decorative polish for a moment. Complete the main task several times with different inputs. Refresh the page, try an empty form, enter long text, and use a narrow screen.
Report concrete symptoms when something fails. Instead of saying the app is broken, describe the page, action, expected result, and actual result. This gives the builder a much better correction target.
- Test successful completion
- Test missing and invalid input
- Test refresh and saved data
- Test navigation from every screen
- Test on a phone-sized viewport
Improve it with real feedback
Share the first version with three target users. Watch without explaining. Record exact phrases and moments of confusion, then group the feedback into must fix, useful later, and personal preference.
Choose one meaningful improvement and implement it. Your portfolio story should show the before, the feedback, your decision, and the new result.
- Fix anything that blocks the main task
- Clarify misunderstood labels
- Reduce unnecessary steps
- Defer features that do not improve the outcome
Publish a credible case study
Publish the working app and check the public URL independently. Remove sample content that could be mistaken for real people or real records. Add a short privacy note if users can submit information.
On Launchda, document your role, the tool, the problem, screenshots, testing, and lessons. Emergent helped you build, but the evidence should focus on your judgement and execution.
- Problem and target user
- Version-one scope
- Prompting and build decisions
- Testing evidence
- Final result and next iteration