|    Intro

All is about Scotty, the Carnegie Mellon mascot.

So, her tour started!

Her first stop was UBitt. Cathedral of Learning, the building, is sooooo BIG!!!

Then she went to MID.

Then UC Buckeley.

And then Stanfard.

Scotty Kept on going and going…

Sometimes she is very tired, so she shoots fireballs to keep herself energized.

Sometimes she bumps into unexpected obstacles.

In more times, she wins!

|    The Work

See the exciting demo video on the right!

Ideation

Our ideation phase started at Friday afternoon 5pm, ended on Saturday 1am.

The former half of the 8 hours was dedicated to opening mind widely and having as many ideas as possible. As a result, we had over 100 ideas, which included applications and games.

In the latter half, we scoped the ideas down. We used a feasibility-impact matrix to analyze every selected idea.  As a result, we wanted to create a collaborative game.

However, after analyzing the feasibility of the idea, we thought the difficulty for the implementation a collaborative game in only 36 hours would be too hard, especially for people who just learned Swift. So we iterated on it, deleted some of the features we talked about, and reached an concrete idea.

Development

As a team of 4 people, we chose agile development mode. Different from the traditional Waterfall development mode, agile develop mode enables designer and developer to work more closely and efficiently, and to iterate product faster.

We divided the project feature by feature and implemented them one by one. For instance, after I transferred the design of the scene to the developers, they began the development work for this feature so that I was able to keep working on the next feature – gravity control. As the interaction and visual designer in this project, I used interaction design method to prototype and made illustrations for the visual. Time was perfectly made use of during the 36 hours.

Remarkably, one develop in our team was working remotely, 1200 miles away. The agile development mode made the team bond tighter and the team members close to each other.

During our breaks, we took selfies!

Presentation & Winning

We presented our version1.0 in McConomy Auditorium, Carnegie Mellon University. There were over 300 hundred people in the audience and over 26 apps/prototypes were presented. In the voting, we won the audience choice award, which meant the majority of the audience voted for our game.

Meet the Team

|    About the Hackathon

The iOS App Challenge Hackathon at CMU is a 4-day-long, non-stop product design and development event at Carnegie Mellon.

Requirements

The iOS Apps that are developed and submitted must meet these requirements in order to be eligible to win the contest and are subject to verification by Apple:

• Must be a native iOS application and written in Swift.
• Must be developed no sooner than the kick-off event.
• Must be fully functional and working at the time of review.
• Must meet submission requirements for the App Store.
• May not contain any previously developed code, except where permitted by the license agreement from the provider. Any open source code must be acknowledged in the About screen or settings bundle of the App.

Growth

Developing a functional app in only 36 hours was challenging. I am glad we survived. This is a proof that I can proudly show people for that I can manage pressure/stress.

UI Spec is important. It’s the designer’s job to get this clear with developears.

In Agile Development, do not go extremely deep in one feature.

A solid IxD is a must for a good visual.