{"id":2,"date":"2022-09-02T16:34:03","date_gmt":"2022-09-02T16:34:03","guid":{"rendered":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/?page_id=2"},"modified":"2022-12-14T17:19:42","modified_gmt":"2022-12-14T17:19:42","slug":"sample-page","status":"publish","type":"page","link":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/sample-page\/","title":{"rendered":"BLOG"},"content":{"rendered":"\n

Week 1 Rally up the team & kick off the project<\/strong><\/p>\n\n\n\n

In the first week, we met with our client to get the design prompt and tried to build up the collaboration system for both the internal and external teams.<\/p>\n\n\n\n

For production:<\/p>\n\n\n\n

We met the team to align with the expectation for project, individual expertises, perferred collaberation mode. <\/p>

We settled on using Slack + Notion + Google suite to manage our projects.<\/p><\/blockquote>\n\n\n\n

For the projects:<\/p>\n\n\n\n

Regarding deeplocal’s working pipeline as a design agency, we brainstormed 12 ideas (2 idead\/people) and created 12 one-liner pitch slides.<\/p><\/blockquote>\n\n\n\n

\n
\n
\"\"
Sample of one-liner pitch<\/figcaption><\/figure>\n<\/div>\n\n\n\n
\n
\"\"
Sample of our brainstorm<\/figcaption><\/figure>\n<\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Week 2 Narrow down the ideas and pitch them to our client<\/strong><\/p>\n\n\n\n

In the second week, we met with our client to get feedback on our initial ideas. Also, we finalized our team collaboration system.<\/p>\n\n\n\n

For production:<\/p>\n\n\n\n

We set up our slack chanel with faculty and clients. We also finazlied the core hour, meetings with faculty and clients. We also set up our working tools like notion, google drive and Figma.<\/p><\/blockquote>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

For the project:<\/p>\n\n\n\n

The clients picked 3 mian directions which they thought are most aligning with design goal and exciting which is Jell-O monster, Jell-O filter and Jell-O Memoir.<\/p>

We also started to play aroudn with Jell-O, conducted some experiment to get more insights and inspiration.<\/p><\/blockquote>\n\n\n\n

\n
\n
\"\"
Jell-O Monster<\/figcaption><\/figure>\n<\/div>\n\n\n\n
\n
\"\"
Jell-O filter<\/figcaption><\/figure>\n<\/div>\n\n\n\n
\n
\"\"
Jell-O Memoir<\/figcaption><\/figure>\n<\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Week 3 ETC quarter and get pushed back by our client<\/strong><\/p>\n\n\n\n

In the third week, we met with the ETC faculty to discuss our project progress and gather feedback. Also, we decided on the monster idea and pitched it to them. We failed to get buy-in which was miserable and sad.<\/p>\n\n\n\n

For production:<\/p>\n\n\n\n

We started to practice the collaberation mode we planed. Most of them went well. The only flaw was the daily scrum was really hard to conduct because the incompatibility of everyone’s schedule.<\/p><\/blockquote>\n\n\n\n

For the project:<\/p>\n\n\n\n

After taking the feedback from the quarter, we directly went into the Jell-O monster idea without syncing it up with our clients. So when we pitched our refined idea to them, we unfortunately got push back.<\/p><\/blockquote>\n\n\n\n

\n
\n
\"\"
Tech feasibility<\/figcaption><\/figure>\n<\/div>\n\n\n\n
\n
\"\"
Experiment with Jell-O<\/figcaption><\/figure>\n<\/div>\n<\/div>\n\n\n\n

For design:<\/p>\n\n\n\n

We finished our team branding kit including poster, half-sheet and team photo.<\/p><\/blockquote>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Week 4 Honed our pitch and successfully sold our idea<\/strong><\/p>\n\n\n\n

In the 4th week, we put a lot of effort into honing our pitch. We learned how to tell the story and how to sell the idea. It was struggling this week, but we finally made it! The client was satisfied and cheered for your pitch.<\/p>\n\n\n\n

For production:<\/p>\n\n\n\n

We add an online scrum meeting on Tuesday and Thursday which suits everyone’s schdule which turned to work better.<\/p>

Also, we reached into a consensus that we will consider the weekly update for clients as psurdo pitches to constantly improve our professional pitch skills.<\/p><\/blockquote>\n\n\n\n

For the project:<\/p>\n\n\n\n

We organized what I had and shaped them into a compelling storyingtelling within 15 mins.<\/p><\/blockquote>\n\n\n\n

\n
\n
\"\"
Logic behind the idea<\/figcaption><\/figure>\n<\/div>\n\n\n\n
\n
\"\"
Storyboard<\/figcaption><\/figure>\n<\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Week 5 Proof of concept and detailed user flow<\/strong><\/p>\n\n\n\n

In the 5th week, we finished our proof of concept, which is the image recognization & polygon generation. Also, we came out with a more detailed user flow.<\/p>\n\n\n\n

For tech:<\/p>\n\n\n\n

Our programmer tried to implement the basic function of our design which is to transfer the real-world image into a virtual 3D subject.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n

For design:<\/p>\n\n\n\n

We came up with detialed user flow and beat sheet. The core of our experience is to create several magic moments including bringing the Jell-O monster to live, humanizing the monster and interacting with the monster<\/p><\/blockquote>\n\n\n\n

\"\"
User flow & beat sheet<\/figcaption><\/figure>\n\n\n\n
\n
<\/div>\n\n\n\n
<\/div>\n<\/div>\n\n\n\n

Week 6 Interaction loop and refined technical solution<\/strong><\/p>\n\n\n\n

In the 6th week, we came out with the core design loop of our experience, which is prompt -> action -> rewarding -> interaction. Also, we finished the technical solution validation for the whole process.<\/p>\n\n\n\n

For design:<\/p>\n\n\n\n

We met the team to align with the expectation for project, individual expertises, perferred collaberation mode. <\/p>

We settled on using Slack + Notion + Google suite to manage our projects.<\/p><\/blockquote>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

For tech:<\/p>\n\n\n\n

We iterated our technical solution for the image recognization and 2D-> 3D transformation, which makes the generated shape more accuracy.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Week 7 Half presentation & Fall break<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

Week 8 Tech demo for customization & ETC playtest day<\/strong><\/p>\n\n\n\n

This week, we finished the basic demo for customization, which allowed users to drag and attach the eye & mouth to the body of Monster. Also, we tested our physical-making stage and demo with around 30 kids and kids.<\/p>\n\n\n\n

For design:<\/p>\n\n\n\n

We created low-fi interfaces and user flow for custimization stage. There are two magic moments which are body generation and feedback after attachment of eye & mouth.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

For tech:<\/p>\n\n\n\n

We implemented the basic functionality of draging & attaching eyes. But its can not be attached on the body shaped if not operating in a front perspective. <\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n

For art:<\/p>\n\n\n\n

We designed our first version of concept art.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n

For playtest:<\/p>\n\n\n\n

Here are top 3 feebacks from playtest:<\/p>

1. Inaccurate and unstable monster body<\/p>

2. It\u2019s hard to drag and drop the eye, and mouth<\/p>

3. Lack of instruction and feedback for eye and mouth<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Week 9 Feeding stage test & narrative design<\/strong><\/p>\n\n\n\n

This week, we iterated our design based on the conclusions we got from ETC playtest.<\/p>\n\n\n\n

For design and art:<\/p>\n\n\n\n

We designed the low-fi design system. Meanwhile, we polished our storyline and created the image of Dr.gelatin.<\/p><\/blockquote>\n\n\n\n

\"\"
Dr. gelatin<\/figcaption><\/figure>\n\n\n\n
\"\"
Low-fi design system<\/figcaption><\/figure>\n\n\n\n

For tech:<\/p>\n\n\n\n

For the stability of the app, we tried to use the Convex Hull solution to decrease the possibility of a broken shape. It helps a lot with the completeness of shape. But the accuracy of shape recognition will be very low.<\/p><\/blockquote>\n\n\n\n

\"\"
Convex Hull solution<\/figcaption><\/figure>\n\n\n\n

<\/p>\n\n\n\n

Week 10 Platform transmission & customization refinement<\/strong><\/p>\n\n\n\n

We changed our platform from iPad to phone. Because image recognition is more stable on the phone, it will be easier for kids to hold and play as well. <\/p>\n\n\n\n

For design:<\/p>\n\n\n\n

We iterated our design system and conducted the high-fi prototype for the customization part.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

For tech:<\/p>\n\n\n\n

We migrated from iPad to phone. For the body generation, we went back to the original mesh solution and let the monster grow up gradually. We also added some particle systems to make it more vivid. For customization, we changed the interaction from drag&drop to click. It performs much better than before.<\/p><\/blockquote>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Week 11 Feeding stage design and implementation<\/strong><\/p>\n\n\n\n

we finalized the experience flow of the feeding stage and started to test it in App.<\/p>\n\n\n\n

For design:<\/p>\n\n\n\n

We brought out our design pillars which are: silliness, surprise, and engagement. On top of that, we designed the feeding flow and decided to use different colors’ jell-O to represent different emotions.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

For tech:<\/p>\n\n\n\n

We realized the color recognition and updated the new 3D asset.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Week 12 Thanksgiving break<\/strong><\/p>\n\n\n\n

<\/p>\n\n\n\n

Week 13 Finished the implementation feeding stage<\/strong><\/p>\n\n\n\n

We implemented the whole experience of the feeding part and kept fixing the trivia before wrapping up.<\/p>\n\n\n\n

For design:<\/p>\n\n\n\n

We updated our design system and finished the package design.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

For tech:<\/p>\n\n\n\n

We finished the feedback loop of 4 emotions and started to work on the ending part: take a photo and save it to the local album.<\/p><\/blockquote>\n\n\n\n

\"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"

Week 1 Rally up the team & kick off the project In the first week, we met with our client to get the design prompt and tried to build up the collaboration system for both the internal and external teams. For production: We met the team to align with the expectation for project, individual expertises, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/wp-json\/wp\/v2\/pages\/2"}],"collection":[{"href":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/wp-json\/wp\/v2\/comments?post=2"}],"version-history":[{"count":48,"href":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/wp-json\/wp\/v2\/pages\/2\/revisions"}],"predecessor-version":[{"id":227,"href":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/wp-json\/wp\/v2\/pages\/2\/revisions\/227"}],"wp:attachment":[{"href":"https:\/\/projects.etc.cmu.edu\/jell-o-played\/wp-json\/wp\/v2\/media?parent=2"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}