Frontend implementation,
Japan-facing UX & messaging, and accessibility support
for international teams.
Sola Studio is an independent frontend-focused practice working with international teams on frontend implementation, product clarity, Japan-facing UX, messaging, structure, Japanese copy direction, review support, and accessibility work.
The work is shaped around clear scope, written context, and the small product decisions that determine what users, stakeholders, and engineers need to understand before delivery, launch, or market-facing communication moves forward.
An independent practice for frontend, product clarity, and accessibility-aware support
Sola Studio is a small independent practice for international teams that need help across frontend implementation, the product decisions that sit between design and code, Japan-facing UX and messaging support, and accessibility review and remediation.
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 assumptions about what the user needs to understand or decide.
Sola Studio works across those boundaries to help make friction easier to locate, explain, and prioritize — whether it appears in the interface, the implementation, the accessibility layer, or the way a page needs to make sense to a specific audience.
For Japan-facing work, that means looking beyond whether the Japanese wording is fluent, and considering whether the UX, messaging, information order, page, message, material, offer, trust signals, and decision flow are likely to be clear and actionable for a Japanese audience.
Yoko Shiina
Independent Frontend Consultant
Frontend / Japan-facing UX & Messaging / Product Clarity
Yoko Shiina — frontend-focused, UX-aware, and product-clarity minded
I help international teams connect frontend implementation, accessibility, UX, and the practical decisions that sit between them.
I work as an independent frontend consultant and engineer, mainly with React, Next.js, TypeScript, API integration, and accessible web development.
Before specializing in frontend engineering, I worked across advertising, customer-attraction strategy, web production, information architecture, and client-facing project work. In that earlier work, I learned to connect business goals, local context, audience behavior, wording, and what people need before they decide to act.
My work often sits where design intent, frontend implementation, component behavior, backend constraints, accessibility, user experience, and product communication meet.
I have worked across B2B SaaS, internal tools, dashboards, Web3 learning products, distributed product teams, and international working environments including Japan, remote teams, and Malta.
That mix of experience shapes Japan-facing work as well: not as a simple native-language check, but as a way to translate implicit market, trust, UX, messaging, structure, and communication gaps into concrete UX notes, website structure, Japanese copy direction, and review findings.
Sola is the studio name. In business-facing contexts, external records, and professional profiles, you may also see my full name, Yoko Shiina.
A few things to know
- in web-related work
- 10+ years
- frontend-focused engineering
- React / Next.js / TypeScript
- accessibility certification
- IAAP CPACC
- Japan-facing UX, messaging, and product communication
- Japan + international context
What you can ask for help with
The current services for international teams focus on frontend capacity, Japan-facing UX, messaging, structure, Japanese copy direction and review support, accessibility work, and practical follow-up support.
Frontend Partner
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.
Japan Bridge
Japan-facing UX, messaging, structure, Japanese copy direction, and review support for teams preparing or improving Japanese pages, messages, materials, customer journeys, or inquiry paths.
Useful when a team needs to clarify Japan-facing UX, messaging, information order, trust signals, decision flow, and Japanese copy direction before design or production, or review existing Japan-facing materials to understand where trust, clarity, or user hesitation may still be blocking action.
Accessibility Review
A scoped review of selected pages, flows, forms, screens, or components to identify accessibility issues, priorities, and practical next steps.
Useful when your team wants to prepare for remediation, improve key web journeys, or understand what may be suitable for frontend implementation within a clear scope.
Accessibility Remediation Support
Scoped frontend implementation support for agreed accessibility issues, especially where React, Next.js, TypeScript, forms, flows, reusable components, or component-based UI are involved.
Useful when your team already has review findings, audit results, or issue lists and wants practical support addressing selected issues within an agreed frontend scope.
Additional support after delivery
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.
Structured collaboration for distributed frontend and product work
Remote collaboration works best when communication is clear by design.
The work is structured around written handoffs, defined scope, visible decisions, and check-ins at agreed times.
This setup works well for teams that already use tickets, async updates, documentation, and structured delivery habits.
- Async-friendly collaboration
- Structured handoffs and written decisions
- Clear context, rationale, and next steps
- Comfortable with agile workflows, tickets, and iterative delivery
The technical base behind the work
The work is grounded in frontend implementation and practical product delivery, while staying connected to UX, accessibility, and product decisions.
Frontend
- JavaScript10yrs
- TypeScript4yrs
- React4.5yrs
- Next.js3yrs
- HTML510yrs
- CSS310yrs
Backend / Data
- Ruby1yrs
- Ruby on Rails1.5yrs
- Java0.5yrs
- Supabase3yrs
- API連携4yrs
- DB設計1yrs
- SQL1yrs
State & Data
- REST APIs4yrs
- Redux2yrs
- Zustand0.5yrs
- Context API2yrs
UI
- Material UI2.5yrs
- Tailwind CSS2yrs
- SCSS4yrs
- Storybook1.5yrs
- Figma3.5yrs
- Sketch2yrs
Testing
- Jest4yrs
- React Testing Library4yrs
- Cypress0.5yrs
- Playwright0.5yrs
How this work took shape
Client-facing foundation
From client strategy and web production
Earlier work in advertising and customer-attraction strategy in Tokyo shaped the way I look at audience, local context, business goals, wording, and what people need before they decide to act. That work later connected into web production, information architecture, wireframes, and client-facing project work.
This became the foundation for connecting business context, user expectations, language, trust signals, and how information is presented in product and service interfaces.
Engineering transition
Into software engineering and distributed collaboration
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
Frontend work across SaaS, internal tools, and MVPs
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, component behavior, and team decision-making.
International context
Working and living across Japanese and international environments
Through international teams, remote collaboration, and life in Malta, I learned to see Japanese communication and product assumptions from both inside and outside.
This shaped the Japan Bridge lens: explaining implicit market, trust, UX, messaging, and communication gaps in a way international teams can discuss and act on.
Sola Studio
Independent frontend and product support
Sola Studio brings these threads together: frontend implementation, accessibility review and remediation, 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.
Credentials and technical foundation
These credentials support the main areas of Sola Studio's work with international teams: accessibility, frontend engineering, product collaboration, and structured delivery.
- IAAP CPACC2025-11
Accessibility foundation across disability types, standards, inclusive design, and organizational accessibility practice.
- Certified ScrumMaster®2025-02
Scrum, team collaboration, sprint-based work, retrospectives, and delivery process awareness.
Product ownership, prioritization, backlog thinking, and product value decisions.
- Google UX Design Certificate2025-04
User-centered 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
What people say about working with me
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."
Writing on UX, frontend work, language, and product friction
I also write in English about UX, frontend work, language, accessibility, and the small product frictions that are easy to overlook in everyday delivery.
- The UX Lesson I Learned in a Quiet Tokyo SalonPublicationMedium Boost
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.
Writing on UX, accessibility, frontend work, and product friction
Writing is one way Sola Studio makes its thinking visible: small product frictions, UX and accessibility observations, frontend work, language, and the gaps that shape how digital services are understood and used.
Some essays have also been Medium Boosted or featured by UX publications.
Selected Medium essayMedium BoostedFeatured by UX CollectiveThe UX Lesson I Learned in a Quiet Tokyo SalonA personal essay about turning local observation and a salon owner’s quiet vision into customer-facing messaging — an early lesson in emotional insight, trust, and UX before the term “UX” entered the frame.
human-centered designemotional designstorytellingux design
Selected Medium essayFeatured by UX CollectiveFrom Universal Design to Personalized Interfaces — Rethinking AccessibilityAn essay questioning whether “one interface for everyone” is enough for real inclusion, and exploring how accessibility, Universal Design for Learning, and adaptive UI can point toward more personalized digital experiences.
inclusive designuniversal designuxaccessibility
UX Lens field noteSola Journal / UX LensCasual Chat, Serious CancellationA cancellation chat felt lightweight, but lacked the confirmation and traceability needed for a higher-stakes service request.
customer supportcancellation flowconfirmation & traceability
Who this is built for
A good fit for teams that need:
- frontend implementation support without opening a full-time role
- accessibility review and scoped frontend remediation support, especially for forms, flows, and component-based UI
- a Japan-facing website, page, message, material, offer, or flow that needs UX, messaging, structure, Japanese copy direction, or review beyond translation
- someone who can work across UI, code, API collaboration, and product clarity
- clear written communication and structured async collaboration
- independent senior-level support rather than a large agency setup
Better handled elsewhere if you need:
- a large agency team with multiple roles bundled together
- brand identity or visual design as the main deliverable
- backend infrastructure ownership
- constant real-time availability as the main working model
- individual coaching, mentoring, or personal support services
- full-service localization delivery, professional translation production, or broad Japan market-entry consulting
Have a frontend, Japan-facing UX, or accessibility question?
Some projects start with a clear implementation need. Others start with a pattern the team can already see, but has not fully mapped yet: a confusing flow, an unclear decision, a Japan-facing page that does not yet feel ready, or a mismatch between what the interface says and what the product needs users to understand. The first step is to make the situation easier to read, then clarify the UX, messaging, structure, review, or implementation step that may be worth considering next.