When students consider entering the tech field, the story often begins with a significant moment: winning a robotics competition, attending a coding camp, or discovering a passion for math. But design projects don’t always begin with dramatic milestones. Sometimes, they start with something as simple as recognizing a frustrating habit, like endless social media scrolling.
By observing patterns, such as when scrolling occurs, what triggers it, and how it affects a person, students can begin to identify opportunities for change. Instead of treating technology as something that controls behavior, the goal is to design tools that support healthier choices. For example, ideas might include a gentle reminder after extended scrolling or a smarter break planner that respects personal time.
This approach highlights an important lesson: meaningful design doesn’t always begin with a grand idea. It begins with paying attention to everyday experiences and turning those small observations into practical solutions.
Build a Strong Foundation in Computer Science
Step 1: Identify a Habit or Problem to Solve
User research is often associated with companies running surveys, conducting usability tests, or analyzing clicks. However, the first “user” to study can be oneself. By tracking personal habits for a week, such as when apps are opened, what triggers the action, and how it feels afterward, patterns start to emerge. For example, many students discover they reach for social media during transition times: before homework, after school, or even in short breaks.
These insights reveal that scrolling is not always about enjoyment but often about habit and inertia. More importantly, they highlight how apps are intentionally designed to shape behavior and attention. Recognizing this is a powerful step in UX design: it shows that technology not only reflect behavior but also actively influences it.
Step 2: Track Your Behavior and Gather Insights
Curiosity often leads to exploring concepts like persuasive design, a term that describes how apps are built to capture and hold attention. Books such as Hooked by Nir Eyal and resources from the Center for Humane Technology explain how features like infinite scroll, swipe gestures, and unpredictable notifications operate much like slot machines. These tools are not just conveniences; they are deliberate strategies to keep users engaged.
Understanding persuasive design reveals how an app’s interface can influence behavior more than most people realize. Once that connection is clear, a powerful design question emerges: How can the same principles be applied in reverse to support focus and productivity?
Aralia Students Are 3x More Likely to Place Top Computer Science Competitions
Step 3: Sketch Your App and Plan Its Features
The process doesn’t begin with coding but with paper. Sketching out ideas helps clarify what an app might look like if it were designed to manage, rather than suppress, everyday habits. Key features could include:
- Viewing daily tasks at a glance
- Setting focused blocks of study time
- Taking breaks without slipping into endless scrolling
- Reviewing how time is spent each day
Once the basic layout is clear, tools like Figma can be used to transform sketches into visual mockups. No coding is required, just thoughtful design choices about layout, buttons, reminders, and interactions. The goal is to create a tool that encourages focus and reflection rather than stress or guilt.
At this stage, the purpose isn’t to build the next big startup. It’s simply to design a small, functional solution that addresses a real problem.
Step 4: Build a Simple Prototype
Once the design feels solid, the next step is to bring it to life. Starting small makes the process manageable. Free resources such as freeCodeCamp and beginner-friendly JavaScript tutorials on YouTube can provide the basics. While concepts like functions or state management may feel challenging at first, connecting them to a personal project gives the learning purpose.
The first working prototype doesn’t need to be complex. A simple version, such as a to-do list paired with a timer, can demonstrate the idea in action. Even with limited features, the key achievement is creating a tool that supports better habits and provides a sense of control over time.
Step 5: Test, Get Feedback, and Improve
After creating a basic prototype, the next step is to test it as both designer and user. Observe how the app feels in real use: Are tasks overwhelming? Do notifications motivate or annoy? Collect insights from personal use and small test groups if possible.
Use this feedback to make small but impactful changes. Iteration is key; each adjustment brings the app closer to an experience that truly supports focus and productivity. Remember, design isn’t just about visual appeal; it’s about shaping how people interact with a tool.
By observing honestly and experimenting deliberately, students can understand real user needs, even when the first user is themselves. This step reinforces the principle that technology is a tool for problem-solving and thoughtful experience design.
Take ACSL Competition Preparation with Aralia
At Aralia, the ACSL Competition Prep program helps students build the skills and confidence needed to excel in the American Computer Science League. The course includes two weeks of foundational programming followed by focused sessions on all 12 ACSL topics, with off-topic problems before each contest to boost problem-solving skills. Taught by a former Computer Science teacher at The Dalton School and an award-winning ACSL coach, the program offers expert instruction and proven mentorship to help students strengthen their problem-solving abilities and prepare them for success.
ACSL Competition Prep
The program begins with two weeks of dedicated programming practice to provide participants with an opportunity to enhance their skills. Subsequently, each of the 12 ACSL topics is allocated a two-week period, allowing ample time for in-depth exploration and understanding. Prior to each contest, participants are presented with two programming problems that are intentionally unrelated to the current topics. These problems are designed to enhance the coder’s skills and foster comfort in tackling diverse challenges.
