Loading...
Sola Studio is an independent frontend-focused practice working with product teams on implementation, accessibility readiness, and practical product support.
The work is shaped around clear scope, written context, and the small product decisions that often sit between design, code, accessibility, and delivery.
Sola Studio is a small independent practice for product teams that need help across frontend implementation, accessibility, and the product decisions that sit between design and code.
Many product issues do not belong to one layer only. A screen-level problem may involve frontend patterns, content structure, accessibility, data flow, or unclear ownership between roles.
Sola Studio works across those boundaries to help locate, explain, and prioritise friction — without adding agency overhead.
An independent frontend partner working across implementation, product clarity, and cross-functional collaboration.
I am a frontend-focused full-stack engineer working mainly with React, Next.js, TypeScript, API integration, and accessible web development.
My work often sits where design intent, frontend implementation, backend constraints, and user experience meet.
I have worked across B2B SaaS, internal tools, dashboards, Web3 learning products, and distributed product teams.
Sola is the studio name. In business-facing contexts, external records, and professional profiles, you may also see my full name, Yoko Shiina.
The current services for EU and UK teams focus on frontend capacity, accessibility readiness, and practical follow-up support.
Ongoing React / Next.js / TypeScript implementation support for your existing team context and codebase.
Useful when frontend work needs to keep moving, but opening a full-time role is not the right next step.
A focused review of selected pages and flows against WCAG 2.2 AA, with prioritised findings and practical next steps.
Relevant for European-facing web products preparing for accessibility improvement, remediation planning, or EAA-aware review.
Follow-up consultation, PR review, and scoped implementation support after an engagement is completed.
Designed for practical next steps without reopening a full engagement each time.
Remote collaboration works best when communication is clear by design.
The work is structured around written handoffs, defined scope, visible decisions, and regular check-ins at agreed times.
This setup works well for teams that already use tickets, async updates, documentation, and structured delivery habits.
The work is grounded in frontend implementation and practical product delivery, while staying connected to UX, accessibility, and product decisions.
Frontend
Backend / Data
State & Data
UI
Testing
Client-facing foundation
Earlier work in advertising, web production, information architecture, wireframes, and client-facing project work shaped the way I look at user needs, business goals, and communication gaps.
This became the foundation for connecting business context, user expectations, and how information is presented.
Engineering transition
Through Microverse and remote engineering work, I moved further into software development through distributed teamwork, pair programming, peer review, and collaboration across regions and time zones.
This shaped the way I work with written communication, peer review, async collaboration, and distributed teams.
Product engineering
Recent work includes B2B SaaS, internal tools, dashboards, Web3 learning products, API collaboration, data flow, and frontend implementation in async teams.
This is where the current Sola Studio focus became clearer: product-facing frontend work that connects implementation with usability, accessibility, and team decision-making.
Sola Studio
Sola Studio brings these threads together: frontend implementation, accessibility, UX clarity, and structured collaboration for teams that need practical support.
The work is designed for teams that need someone who can understand the product context, work with the code, and help clarify the practical next step.
These credentials support the main areas of Sola Studio's work with EU and UK teams: accessibility, frontend engineering, product collaboration, and structured delivery.
Accessibility foundation across disability types, standards, inclusive design, and organisational accessibility practice.
Scrum, team collaboration, sprint-based work, retrospectives, and delivery process awareness.
Product ownership, prioritisation, backlog thinking, and product value decisions.
User-centred design, UX research basics, information architecture, prototyping, and design iteration.
Remote software development training with pair programming, code review, and international collaboration.
Software design fundamentals, maintainability, and object-oriented design thinking.
Additional credentials and professional history are available on LinkedIn. LinkedIn
Selected recommendations from people I have worked with across engineering, product, and project settings.
"Yoko’s projects were consistently high quality and often ahead of schedule. She combines best practices with creative problem solving, and uplifts everyone around her."
"She possesses a rare combination of technical prowess and language proficiency. Her adaptability and contribution to our TypeScript/React projects were invaluable."
"Her keen eye for design and user experience, combined with her frontend skills, made her a key contributor to our projects."
"She breaks down complex topics into simple steps and completes projects ahead of schedule. Her working style makes collaboration smooth and effective."
I also write in English about UX, accessibility, frontend work, communication, and the product friction that is easy to overlook in everyday delivery.
UX Collective (Bootcamp)
A reflection on how an unexpected moment in a small Tokyo salon became my first real UX lesson — and how emotional insight can reshape the way we design experiences.
UX Collective (Bootcamp)
An exploration of why “universal design” is not always enough — and how more adaptive, personalized interfaces can better support real users with diverse needs.
JavaScript in Plain English
Lessons from designing and shipping a fully keyboard-accessible app — from uncovering edge cases to using accessibility as a driver of frontend architecture.
A good fit for teams that need:
Probably not the right fit if you need:
Some projects start with a clear implementation need. Others start with a pattern the team can already feel, but hasn't fully mapped yet. The first step is to make the situation easier to read, then clarify what may be worth considering next.
Start an enquiry