How to use hackwithus and the tiun × microlaunch challenge

The microlaunch challenge on Hackwithus gives you a focused path to ship a product with tiun: enter, add the tiun SDK, and launch in week four. Use this guide to prepare your submission, verify the integration, and share your build with the community.

Before you enter the challenge

Prepare a small product idea or an existing project that can be improved and launched within the challenge timeline. It might be a focused tool, a workflow product, or another project that can benefit from a clear tiun integration. The deciding factor among startup-builders products is whether they support this exact workflow.

Review revenue-focused hackathon products if you need examples of products built around a clear path to revenue. Then complete this checklist:

• [ ] Define the problem your product solves.
• [ ] Choose one primary user and use case.
• [ ] Decide what you will launch in week four.
• [ ] Set up a working development environment.
• [ ] Join the Hackwithus community chat for questions, teammates, and feedback.

Keep the scope narrow. A complete, understandable product is more useful for the challenge than a long list of unfinished features.

1. Enter the tiun × Microlaunch challenge

Start on Hackwithus and follow the challenge entry instructions. Read the hackwithus submission guide before building so you know what the final submission should contain.

The guide should shape your project decisions from the beginning. Write down:

1. The product name and one-sentence description.
2. The user problem and your proposed solution.
3. The tiun feature or workflow your product will use.
4. The launch URL or working demo you expect to submit.
5. The evidence you will show that the product works.

The challenge has a growing prize pool of up to $10K, with a dedicated jury reviewing submissions. Treat the prize as an incentive, not as a substitute for a usable product or clear presentation.

2. Add the tiun SDK integration

Use the Hackwithus starter kit to avoid unnecessary setup work. It includes templates and examples tailored to tiun builders. Follow the kit’s implementation pattern, then adapt it to your product’s main user flow.

For a practical tiun integration challenge, verify the following:

• The tiun SDK is installed and configured correctly.
• The integration runs in the intended product flow.
• A new user can reach the tiun-powered feature without confusion.
• Errors are handled clearly.
• Your demo uses realistic sample data.

Keep a short record of what you changed. Include the relevant integration steps in your submission rather than assuming reviewers will infer them.

After implementation, test the complete path from the first screen to the tiun result. If the feature works only in a local environment, resolve that before launch week.

3. Launch and submit in week four

In week four, publish the product and prepare the submission. Use the rally support tools to share the build and attract votes, while keeping your description focused on the user problem and working result.

Before submitting, run this final check:

• [ ] The product is accessible through the submitted link.
• [ ] The tiun integration works in the public build.
• [ ] The demo explains the main workflow quickly.
• [ ] Screenshots or a short walkthrough show the completed feature.
• [ ] The submission follows the required format.
• [ ] The launch message includes a direct request for useful feedback.

If you are comparing your project with other tiun integration challenge products, compare implementation clarity and user value, not just feature count. Projects in hackathons often stand out when the submission makes verification easy.

Common mistakes and final verification

Avoid starting with too many features, hiding the tiun integration behind an unclear interface, or waiting until launch week to test the public version. Also check that your description explains what users can do, rather than only listing technologies.