sahil khoja - dangle

back to top



As the first hire and designer on our team of two, I learned that design isn't limited to assets and images used within an application; there's prototyping, user testing, marketing, and developing a sign up page. As the only other person on the team (aside from the founder), I took the owness upon myself for the second iteration of Dangle, along with having mockups, wireframes, and assets ready to be handed to a iOS Developer on contract.


Develop the initial designs and create a seamless parent-side experience.


Before I came on to the team, Dangle had outsourced its development work in creating a landing page to get some initial traction, which was poorly designed. The engagement, CTA's, and the value that Dangle was supposed to bring to its users was difficult to understand. Laramie, the founder, and I tore down the existing site and I developed the current one that we used to accumulate over 1000 email sign ups.


Version 1.0's user interface was a bit scattered with too many variables, which would confuse any parent who wants to use Dangle. Initally, the parent would award their child points for completing certain tasks and those points would be use to get carrots, which in turn would allow the child to earm some sort of present. The onboarding just to explain how points accumulate to carrots which later accumulate to a present would've been extremely cumbersome, and instead I developed a flow in which points accumulate to a single carrot. That carrot would allow the child to earn what they would like.

Task Flow - Before

Task Flow - Explore

Task Flow - After

Potential Full Wireframe


With the wireframes and survey data in check, I was able to create a prototype in Framer of the application for the parents side. The prototype would contain the core of the application (viewing tasks, adding tasks, viewing carrots, and image verification). This flow would also be used to show our iOS Developer what we were invisioning.


Working with a startup as the second hire can be extremely difficult, but rewarding as well. Being the only designer on the team, I was able to make key decisions to the core of the application, along with testing these assumptions on early users. I also learned how to use various prototyping tools such as Framer and Invision, along with handing off all-things design related to an experienced developer. If you would like to know more about my work at Dangle, shoot me a message since some of work is still under NDA!