04 / Product concept

FocusNest.

FocusNest is a productivity app concept for young adults. It brings coursework, commitments, and everyday tasks into one place. In a team of three, I led the UI design and shaped how capturing a task, seeing it in time, and choosing what to focus on next connect in the Figma design.

Role
UI design lead · Interface, visual system, and screen design
Team
Three-person team
Format
Product pitch and high-fidelity interface concept
Methods & tools
Figma · Information architecture · Mobile UI · High-fidelity screens
FocusNest concept presentation with app icon, wordmark, and task entry and calendar screens
The presentation artwork from our Figma file. The walkthrough below picks out individual decisions from the larger design boards.
01 / The problem

A planner for the whole day.

Coursework is only one part of a young adult’s schedule. Classes, part-time work, clubs, money, health, and personal plans all compete for the same week, but most tools only handle one of them. So people end up juggling a school planner, a calendar, a notes app, and their memory.

FocusNest is an app concept that brings academic, extracurricular, finance, wellbeing, and personal commitments into one planning space. I decided how the app looks, how its screens connect, and how the design keeps very different kinds of tasks readable in one list.

My part

UI design lead. I owned the screen designs, the visual system (type, colour, category treatment, and the Fn identity), and the high-fidelity Figma screens and presentation boards.

The team’s part

The three of us shaped the concept and pitch together. My design decisions are the ones described on this page.

02 / Structure

One journey, four clear moves.

I designed the product around a simple information architecture. A mixed task list is the home base, categories give context, a calendar shows time, and focus and analytics tools cover what happens after planning. Every screen belongs to one of four moves, which kept the app from becoming a pile of features.

  1. 01 See

    Scan upcoming tasks and their written category labels.

  2. 02 Capture

    Add a description, section, and date in a contextual sheet.

  3. 03 Place

    Switch between month and week views to understand time.

  4. 04 Focus

    Open the timer or review activity from the wider menu.

03 / Figma walkthrough

The central task journey.

These three states from my Figma board tell the story better than the whole board at once. Choose a step to see the screen, the interaction, and the reasoning behind it.

Home / mixed context

Let the next task come into focus.

Names and dates do the primary reading work. Small category names and coloured rails make very different commitments easier to distinguish in one list.

  • The page title orients the user before the content.
  • The add control stays within reach after scanning.
  • Colour repeats with text, so it is not the only category signal.
Original design / Figma Community

Explore the file behind the screens.

This walkthrough covers the core task journey. Open our Figma Community file to explore every screen and board.

Open Figma file (opens in a new tab)
04 / Entry and navigation

Build a path into the product.

I gave new and returning users separate routes from the entry screens. Inside the app, one menu holds search, analytics, the Pomodoro timer, settings, and category views. The design question I kept asking was where each destination belongs: what deserves a place on the main screen, and what can wait one tap away.

01 / Entry

One primary action per screen.

I kept the sign-in view dark and quiet so the account decision stays small. In a built version, form fields, recovery, and account creation would each need clear labels and visible keyboard focus.

See entry board ↗
02 / NAVIGATION

Group the deeper tools.

I kept task capture central and moved secondary tools into the menu. Each category has a written name as well as a colour, so it means the same thing on a task card as in a filtered view.

05 / Focus and reflection

Planning leads to doing.

Planning only matters if it leads to doing. I put the focus timer next to the schedule, so starting a work session follows directly from seeing what’s next. The analytics and profile screens close the loop by letting someone look back at how their time went. The numbers on these screens are sample data I designed to show the layout.

Do the work Timer and schedule share a context.
Reflect on it Profile metrics are illustrative sample values.
06 / Visual system

Bright signals on a calm base.

I built the visual system around DM Sans, the “Fn” mark, and a blue and yellow wordmark. Every colour has a job: charcoal for the entry and dark surfaces, blue for primary actions, yellow for brand energy, and secondary colours for task categories.

Fn FocusNest
Charcoal #24282C

Anchors entry and dark surfaces.

Blue #087AB8

Directs attention to primary actions.

Yellow #FFBF00

Gives the identity warmth and flags Academic tasks.

Mint #00BFA5

Distinguishes extracurricular tasks.

The board also uses red, purple, and other category colours. My rule was that each category colour always appears with its written name, so the meaning holds in the list, the menu, and the calendar. In a production build, I’d contrast-test each colour against both themes.

Open visual-system board ↗
07 / Fidelity and next step

What I’d do next.

FocusNest ended as a pitch with high-fidelity Figma screens and presentation boards. It wasn’t built or tested with users. Looking back with more experience, here’s how I’d move it forward.

  1. 01 / Link the core loop

    Build a clickable prototype that connects signing in, adding a task, scheduling it, and starting a focus session. That loop is the product.

  2. 02 / Test the category model

    Run task-based sessions with students to see whether the categories match how they actually think about their week, or whether they need to create their own.

  3. 03 / Check the labels and controls

    Watch where people hesitate in the add-task sheet and the menu. Those moments would show which labels need rewriting.

  4. 04 / Accessibility before build

    Review keyboard operation, screen-reader labels, focus order, text scaling, and contrast in both themes before a single screen goes to development.

08 / Reflection

What the concept is trying to earn.

A planning tool becomes useful when someone can capture a commitment and then decide where their attention should go next.