The Ulsan Youth Support Center took the challenges from a company demand survey and made them the hackathon's topics.
From October 1 to November 6, 54 young people formed 10 teams
and turned those challenges into apps by describing them to an AI.
The October 30–31 hackathon was two days in the middle of that month to spur development.
The first hour, starting at 2:30pm on day one, covered how to use Bana and how to build each type of challenge.
Teams then moved into building and kept going through the next day, while mentors visited every team every two hours to take questions and offer feedback.
How to use Bana and how to build each challenge
Pick a challenge and build the app
Encouragement · Q&A · feedback
Presentations, then back to building
The center gathered ten challenges through a company demand survey.
They covered AI content production, in-house document search, document conversion and review, AI adoption diagnosis, shipbuilding process monitoring, equipment maintenance, manufacturing data analysis, a travel concierge, customer churn analysis, and wellness product planning.
Each team used these challenges as a starting point to decide which app to build.
What the Ulsan Youth Support Center decided was the challenges, the team makeup, and the schedule of the two-day hackathon.
Bana handled one hour of training, a lecture on how to build each challenge, and on-site mentoring.
On November 6, Bana also took part in the judging as an external judge.
No developer tools to install and no servers to set up.
The ten challenges the center gathered are first shown as example apps you can build on Bana, and each team builds its own challenge into an app the same way.
In one hour the session covered how to use Bana, how to write the plan, and how to build each challenge, and teams went right into building.
Two mentors went round every team every two hours, encouraging participation, taking questions, and giving feedback on progress.
Each team's work log is visible on the Bana operations screen, so the center can put participation straight into its results report.
We captured day one, when the training was held, and day two, when teams focused on building.
Flip through them in time order.
Hackathon opening · Oct 30
Before training · Oct 30
Team seating · Oct 30
Wrap-up and questions · Oct 30
Team development · Oct 31Just tell us the number of participants, the schedule, and the challenges you want to cover, and we will put together a training and on-site mentoring plan.
Leave your details and we will be in touch quickly.
We'll be in touch within one business day.