Made by Who Knows
We’re giving you back control over the big picture, by colouring in some of the little ones!
How many times in your life have you spent so long trying to work out what to eat, you’ve ended up too hungry to cook? How often do you sit down to watch or play something, only to realise you’ve spent 45 minutes looking through all the options in your backlog? How often does making a decision keep you from enjoying the outcome? We know that people live busy lives, and that decision fatigue is real. We built Decisions to help relieve some of that burden. In Decisions, you can register an account and start creating personalised lists (e.g. ‘what to cook for dinner’) of options (e.g. ‘soup’, ‘salad’, ‘sandwich’) to be used in a decision-making process. They’re linked to your account, so you can build up your options over time, and edit them whenever you need to. You can invite other users to join groups (e.g. ‘board game night’) if you’re collaborating on a decision, and you’ll all get instant feedback (and notifications!) about any decisions you’re taking part in. Decisions are made using a themed process like ‘This or That’, where users take turns choosing between two options until a winner is crowned. Once you’ve completed a decision, the result is saved to your profile.
The Team
Abby Davis (she/they)
Hey, I’m Abby! I studied English Literature and Philosophy…
in undergrad and Education, Public Policy and Equity at the University of Glasgow for my master’s. I have previously worked in education, and I am really enjoying the opportunity to take my learning in such a new direction. You can usually catch me at a cinema, a concert, or a bookshop.
Alexandre Izumi (he/him)
Hi there, I’m Alex! After years of solving IT mysteries in…
Technical Support, I’m now diving into the world of Software Development. I’m passionate about technology and love the challenge of turning ideas into reality. When I’m not buried in code, you’ll catch me scoring goals on the football pitch or creating music that inspires. I’m excited to bring my technical expertise and creativity to build meaningful software solutions.
Dhiran Sodha (he/him)
Hi! I’m Dhiran, a Physics graduate from the university of…
Warwick. I’m currently exploring software development while preparing for a computer science degree at Edinburgh University. In my free time I enjoy playing tennis, and also two musical instruments – piano and drums.
James Sewter (he/him)
Hey, I’m James an Aerospace Engineering Graduate from the…
University of Sheffield. I am eager to learn as much about software engineering/development as possible and create cool things! When not coding you can find me on a run somewhere in the countryside.
Wren Hawthorne (they/them)
Hi there, I’m Wren! I was a barista for years, but now I…
brew software! I love board games, and giving new life to old tech. I’m interested in crafting accessible, intuitive user experiences, and I’m currently learning about sustainable software development.
Zeineb Mukhtar (she/her)
Hi, I’m Zeineb a biomedical science graduate from the…
University of Reading. I’m interested in building my foundational skills in software development.
Tech Stack
We used a modified MERN stack, replacing Express.js with Koa.js and React with React Native. We utilised JavaScript and TypeScript, as well as Expo Go and socket.io. We were interested in challenging ourselves to learn new technologies, but we wanted to make sure the tools we chose were appropriate for the project. MongoDB allows us to handle dynamic, user-generated data; an idea very much at the heart of our design. socket.io made instant feedback and live collaboration – another core concept for the project – possible, and we decided to work in React Native and Expo Go so we could develop a cross-platform mobile-first application, since we’d all imagined using the app on our phones from the beginning anyway!
Challenges Faced
As we started to plan our project, we became increasingly excited and ambitious about all the features and functionality we envisioned for the project. We had to really challenge ourselves – and each other – to dial in the requirements for our MVP, and to make sure we could complete our project in the time we had available. We also ended up planning to use an almost entirely unfamiliar tech stack, which at times felt a little overwhelming! We managed this as a team by having one or two specialists take the lead on spiking a technology, so everyone in the squad had several points of contact for support during development. Thanks so much for checking out our project! Have a great day!