Mira Sen®

Frontend developer · Bengaluru, India

Fictional portfolio concept

Interfaces withpurpose. Detailswith personality.

I’m Mira, a frontend developer exploring accessible tools for everyday work.

Thoughtfully built.
Always a work in progress.

Explore my work

01 / Selected work

Small tools. Real questions.

Three self-initiated concepts.
Built to learn by doing.

RouteMap concept preview: a commute map with two clearly labeled route choicesWORKHOMEYour morning, mapped.Metro + walk35 minBus + walk48 minILLUSTRATIVE ROUTES · NO LIVE DATA↗ RouteMap
01 — Everyday mobility2026

RouteMap

Comparing commutes shouldn’t mean piecing together five different tabs.

Grain concept preview: a small-shop inventory dashboard with stock levels and reorder labelsgrain.MS▦ Overview▤ Inventory↗ Activity⚙ SettingsA little order. A clearer day.Here's what's on your shelves.PRODUCTS IN STOCKNEEDS A LITTLE ATTENTION2403 to reorderPRODUCTSTOCKSTATUSOat milkFilter coffeeBrown rice18432In stockReorderIn stockLESS GUESSWORK. MORE HEADSPACE.
02 — Calm operations2026

Grain

A clearer view of what’s on the shelf, for the people running the shop.

QuietType concept preview: a dark Markdown editor with a simple note and a quiet toolbarquiettype↗010203040506# Make room for a thought.A blank page. A little space.Nothing between you and the words.- Start somewhere small- See where it takes youMARKDOWNLOCAL DRAFTA LITTLE LESS INTERFACE.
03 — Space to focus2026

QuietType

Writing needs room to breathe, without a toolbar competing for attention.

Concept explorations, not client commissions. All preview data is illustrative.

02 / My toolkit

Good foundations.
Room to grow.

I care about how an interface feels, how it holds up, and who gets to use it. These are the tools I’m practicing along the way.

Semantic HTML01
CSS02
JavaScript03
React04
Accessibility05
Interface testing06

Less magic. More understanding how it works.

03 / Learning in public

One step at a time.

A few milestones in a fictional year of building, questioning, and getting a little better.

  1. Started with the structure.

    Built a semantic HTML foundation, from landmarks to well-labeled forms.

  2. Made the first connections.

    Shipped the RouteMap prototype, exploring accessible commute comparisons.

  3. Asked, “Does it actually work?”

    Explored component testing, focusing on what people can do with an interface.

  4. Put the pieces together.

    Assembled this portfolio. Still curious. Still building.

04 / A small hello

Good things start
with a conversation.

This is a demo portfolio. Copy the sample address to test the interaction.

A sample address, a real interaction.

01 / Concept case study

RouteMap

A commute comparison prototype that puts the trade-offs in one place.

The problem

Commute options are hard to compare when journey time, walking distance, transfers, and access information live in separate views.

Intended users

Bengaluru commuters exploring an unfamiliar journey, including people who need to plan around walking distance or step-free access.

Three implementation decisions

  1. Use structured sample route objects so every option presents the same fields in the same order.
  2. Keep a readable route list beside the map; the map adds context without becoming the only way to understand a journey.
  3. Use explicit filter buttons and predictable sorting, preserving the selected option when comparison settings change.

Accessibility consideration

Label routes with text and distinct line patterns as well as color. Keep filters keyboard operable and announce updated result counts without moving focus.

An honest limitation

This is a concept with illustrative journeys, not a navigation service. There is no live transit feed, verified accessibility data, or field testing with commuters. Routes must not be used for actual travel planning.

Self-initiated concept · HTML, CSS, JavaScript · April 2026
02 / Concept case study

Grain

A calmer inventory dashboard for the people doing a little of everything.

The problem

A small shop’s stock list can become difficult to scan when low inventory is buried among ordinary updates and dense spreadsheet columns.

Intended users

Independent shop owners and staff who need to check shelf quantities, spot items to reorder, and make quick stock corrections.

Three implementation decisions

  1. Separate inventory rows, status labels, and quantity controls into reusable React components with explicit state.
  2. Derive reorder labels from each product’s threshold rather than maintaining a second, potentially inconsistent stock status.
  3. Provide a confirmation step for removing an item and a clear empty state when filters return no products.

Accessibility consideration

Use a semantic table with associated headers, descriptive labels on quantity controls, and text labels for stock status. Preserve a logical reading order when the layout narrows.

An honest limitation

The dashboard is a frontend concept using sample inventory. It has no sales integration, multi-user synchronization, or persistent production database. Its workflow has not been validated with shop staff.

Self-initiated concept · React, CSS · 2026
03 / Concept case study

QuietType

A distraction-free Markdown editor with just enough interface.

The problem

Toolbars, formatting panels, and alerts can crowd out the writing itself. Removing them entirely can also make useful actions hard to discover.

Intended users

People drafting personal notes and short documents who enjoy plain text and want a simple way to review their Markdown.

Three implementation decisions

  1. Use a native textarea for predictable selection, cursor behavior, and keyboard input instead of a custom contenteditable surface.
  2. Separate writing and preview modes with labeled buttons, keeping the draft and cursor position when switching back.
  3. Save drafts locally with guarded storage access, and make the save state visible so an unavailable browser feature never looks like a successful save.

Accessibility consideration

Give the editor a visible label, retain native keyboard shortcuts, and avoid intercepting the Tab key. Keep save announcements polite so they do not interrupt typing.

An honest limitation

This is an editor concept, not a released writing service. Browser-local drafts are not a backup. The concept has no cloud sync, collaboration, or complete support for every Markdown extension.

Self-initiated concept · JavaScript, semantic HTML, CSS · 2026