<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daria Ryazhskikh on Medium]]></title>
        <description><![CDATA[Stories by Daria Ryazhskikh on Medium]]></description>
        <link>https://medium.com/@daria.ryazhskikh.bolt?source=rss-cf7f505f9bd1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wYECKrEs0brDHnJDOy5ewg.jpeg</url>
            <title>Stories by Daria Ryazhskikh on Medium</title>
            <link>https://medium.com/@daria.ryazhskikh.bolt?source=rss-cf7f505f9bd1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 03:25:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daria.ryazhskikh.bolt/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Feature leading at Bolt: More than writing code]]></title>
            <link>https://medium.com/bolt-labs/feature-leading-at-bolt-more-than-writing-code-99a1fa352e2b?source=rss-cf7f505f9bd1------2</link>
            <guid isPermaLink="false">https://medium.com/p/99a1fa352e2b</guid>
            <category><![CDATA[writing-code]]></category>
            <category><![CDATA[bolt]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Daria Ryazhskikh]]></dc:creator>
            <pubDate>Tue, 03 Feb 2026 13:53:21 GMT</pubDate>
            <atom:updated>2026-02-03T13:53:21.467Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cYCeWB_8gtx9nQN8fzjttQ.png" /></figure><p>Being an engineer at Bolt means owning features end-to-end. Not every team has project managers or dedicated architects — instead, engineers lead projects from the initial idea all the way to rollout.</p><p>A feature lead coordinates the work of the feature squad and takes responsibility for making the feature done: designing a technical solution across teams and tech stacks, coordinating work, removing blockers as they appear, and ensuring a smooth rollout.</p><p>The feature lead role is not permanent — it’s assigned per feature and is available to every engineer.</p><h3>Feature lifecycle</h3><p>Feature ideas are owned and managed by the product, but engineers get involved early. Once an idea is approved and prioritised, it moves through a defined lifecycle driven by an engineer acting as the feature lead.</p><p>Below, we describe each stage and its responsibilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*w0FoRcdXd9Gcd_jnx0AY5A.png" /></figure><p><strong>Who:</strong> Product manager and product designer</p><p><strong>What:</strong></p><ul><li>Define the problem space and expected impact</li><li>Develop a detailed UX design</li><li>Organise design critique sessions with engineers and QA</li><li>Align with the dependency teams</li><li>Plan the iterations and milestones</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*m1qZb2qwEQrZATFkU_E_Kw.png" /></figure><p><strong>When:</strong> The feature is prioritised and assigned to the development team</p><p><strong>Who:</strong> Feature lead</p><p><strong>What:</strong></p><ul><li>Prepares the system design document</li><li>Checks and approves it with the stakeholders and other engineers</li><li>Presents a plan at the kick-off meeting, which officially starts the development</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*eE6_jnb8afvLYRO6IQfVnw.png" /></figure><p><strong>When:</strong> Design document is approved, kick-off is done</p><p><strong>What:</strong></p><ul><li>Engineers — write the code and auto tests</li><li>QAs — write the test cases and check functionality</li><li>Feature lead — keeps the track and resolves the blockers</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*EZOcYnw4v-iw_UI2VCt88w.png" /></figure><p><strong>When:</strong> QA, design and product sides give a green light to go live</p><p><strong>Who:</strong> Feature lead or product manager</p><p><strong>What:</strong></p><ul><li>Align on go-to-market strategy</li><li>Gradually release the feature to the public</li><li>Monitor the technical stability and make sure production bugs are solved</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*5s_JPAvlr4I7cr33zrBbpA.png" /></figure><p><strong>When:</strong> The feature is technically stable</p><p><strong>Who:</strong> Product manager</p><p><strong>What:</strong></p><ul><li>Monitors the performance metrics</li><li>Once enough data is collected, decides whether the feature should stay or plans further iterations.</li></ul><h3>System design</h3><p>Every feature at Bolt starts with a plan. The design document captures <em>why</em> we’re building the feature, <em>what</em> it should do, and <em>how</em> it will be implemented.</p><p>The document typically includes:</p><ul><li><strong>Introduction</strong> — background and context</li><li><strong>Requirements</strong> — scope and definition of done</li><li><strong>Solution</strong> — the technical approach</li><li><strong>Success metrics</strong> — how we measure impact</li><li><strong>Rollout plan</strong> — how and to whom the feature is going to be released</li></ul><p>Below, we break down each section in more detail.</p><h4>Introduction</h4><p>The product manager writes this section early on to describe the high-level problem. It outlines what is broken, what is missing, and the opportunity at hand, setting the context for the entire team.</p><h4>Requirements</h4><p>This section defines what the feature will do — and what it will not.</p><p>Clear scope boundaries help us ship an MVP quickly, validate it, and decide whether further investment makes sense.</p><p>Since the most challenging and longest part of any feature is implementation, engineers are best positioned to advise on reducing complexity, making trade-offs, and postponing non-essential ideas.</p><p>Of course, the leading engineer doesn’t decide the scope alone. They discuss it with the product manager, product designer, and other stakeholders.</p><h4>Solution</h4><p>This is the core of the design document. It describes the technical solution: flows, APIs, database schemas, protocols, and the implementation plan.</p><p>The structure depends on the feature. It can be split by platform (backend, iOS, Android) or organised by user stories, which also helps QA prepare test cases. By the end, the document should be detailed enough to be turned directly into development tasks.</p><p>The feature lead develops the solution together with other engineers. Having multiple perspectives early helps catch mistakes, surface edge cases, and improve the overall design. Mobile features usually involve backend, iOS, and Android teams, which already makes for a solid set of involved people. Consulting engineers from other teams also add valuable insight.</p><p>Before any development starts, we make sure:</p><ul><li>The solution is realistic within the agreed timeframe</li><li>It follows company standards</li><li>It’s approved by stakeholders and relevant engineers</li></ul><h4>Success metrics</h4><p>When planning a feature, we always define what success looks like.</p><p>Some features — like migrations or minor design changes — are considered successful if they don’t break existing flows. Others are expected to move key metrics such as revenue, cancellation rates, support contacts, or conversion funnels.</p><p>For new functionality, we also think ahead: which events to track, which funnels matter, and how future iterations will be evaluated. The design document includes a detailed analytics plan with event names, parameters, and expected flows. It’s especially important for mobile development, as two different codebases must be aligned.</p><p>While product managers and data analysts own the final metrics, engineers usually propose the tracking plan, as they know the integration points best. All metrics and analytics plans are reviewed and approved collaboratively.</p><h4>Rollout plan</h4><p>At Bolt, we typically release client features as A/B tests. We follow trunk-based development but keep new functionality hidden until we verify it. Our internal experimentation system handles user enrollment and tracks the results.</p><p>Each feature has its own rollout plan. Some features are targeted to specific locations or limited to only one mobile OS. This part is defined in close collaboration with the product manager.</p><p>Features are often tested on employees first, which already provides a significant audience and fast feedback. Public rollout may start with a small percentage of users to validate the main funnels, followed by a larger audience to collect experiment data.</p><h3>Development stage</h3><p>Once engineers and stakeholders approve the design document, development starts.</p><p>Tickets and estimates can be created by the feature lead or shared across the squad — whatever works best for the team. The feature lead writes code in their own stack, but their responsibility is broader: <strong>getting the entire feature on all sides over the finish line</strong>.</p><p>That means:</p><ul><li>Tracking progress across all platforms</li><li>Unblocking people</li><li>Handling surprises</li><li>Having a realistic sense of when the feature will be done</li></ul><p>Communication is essential. We usually have regular sync meetings and a dedicated Slack channel for the feature. Development and writing test cases often go in parallel, so the software and QA engineers analyse the flow independently and have a dedicated place to raise concerns if any. The earlier we spot a problem, the easier it’s to solve.</p><p>The feature lead can also organise ad hoc meetings, for example, for interim demos or test case reviews. We don’t have a dedicated automation QA role, so engineers handle test automation, and coverage should be chosen wisely.</p><h3>Feature launch</h3><p>A feature is considered done when:</p><ul><li>Development is finished on all required platforms</li><li>Test cases are written, and critical ones are automated</li><li>QA gives a green light</li><li>Mobile app updates are published in stores</li></ul><p>Now it’s time to launch, according to the rollout plan defined in the design document. That can be done by either the product manager or the feature lead.</p><p>The rollout stage may include collaborating with marketing, support, and local teams to promote the feature and set up the feedback loop.</p><p>Launch is also the moment to give credit. The feature lead introduces the feature in the announcements Slack channel and mentions everyone involved.</p><p>During the early rollout, the feature lead closely monitors technical and product metrics to catch production-only issues. Once the feature is stable, the team moves on to the next project, and the product side handles further experiment tracking and analysis.</p><h3>Conclusion</h3><p>The feature leading shifts your focus from just implementing tasks to thinking about outcomes. You still write code, but you also:</p><ul><li><strong>Analyse</strong> funnels and build product intuition</li><li><strong>Influence</strong> product decisions</li><li><strong>Design</strong> architecture with other teams and tech stacks in mind</li><li><strong>Coordinate</strong> the work of the development group and help them work efficiently</li><li><strong>Plan</strong> <strong>post-feature work</strong>: rollout, monitoring, and follow-ups</li></ul><p>That level of trust and responsibility makes engineering at Bolt more demanding than just writing code. It pushes your limits — and your growth never stops.</p><h3>Join us!</h3><p>Grow fast, make a global impact, and help make cities for people, not cars. Explore hundreds of open roles <a href="https://https//bolt.eu/en/careers/">on our careers page.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99a1fa352e2b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bolt-labs/feature-leading-at-bolt-more-than-writing-code-99a1fa352e2b">Feature leading at Bolt: More than writing code</a> was originally published in <a href="https://medium.com/bolt-labs">Bolt Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a cross-platform design system]]></title>
            <link>https://medium.com/bolt-labs/building-a-cross-platform-design-system-2674bb314787?source=rss-cf7f505f9bd1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2674bb314787</guid>
            <category><![CDATA[cross-platform]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Daria Ryazhskikh]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 12:41:33 GMT</pubDate>
            <atom:updated>2025-12-15T12:41:33.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Te49c7zLCq7ubvwt.png" /></figure><p>Bolt is a product company with multiple verticals and independent codebases using different tech stacks for different kinds of front-end:</p><ul><li>Native mobile applications for <strong>Android</strong> and <strong>iOS</strong></li><li><strong>React Native</strong> mobile applications</li><li><strong>Web applications</strong> — Bolt homepage, internal tools, customer portals and so on</li></ul><p>Each vertical works independently with its own teams and practices. Each product has its own UX challenges to serving the needs of millions of people in over 50 countries. Still, we need a unified approach to design:</p><ul><li>To keep our products visually consistent</li><li>To comply with accessibility requirements</li><li>To avoid reinventing the same UI patterns repeatedly</li><li>To define common terms for designers and engineers in all teams, for easier collaboration within and between teams</li></ul><p>In this article, I’ll describe how our <strong>Design System</strong> works at <strong>Bolt</strong> — how it’s structured, what challenges we face, and how we solve them.</p><p><em>(Disclaimer: my experience is mainly from the Android side, in both product and platform teams.)</em></p><h3>Structure and ownership</h3><p>Company-wide solutions can’t rely on individual enthusiasm alone; they need structured ownership and alignment across all roles. And that’s how it works in Bolt.</p><h4>Actors</h4><p><strong>Design System Team</strong> — Designers who own the design system as a product. Although there are no engineers, their work requires strong technical awareness and a deep understanding of product needs.</p><p><strong>Platform Teams</strong> — Engineers who own the application foundations: architecture, infrastructure, and best practices per platform. They are responsible for the technical implementation of the Design system.<br>We have dedicated platform teams for <strong>Mobile (Android/iOS)</strong>, <strong>React Native</strong>, and <strong>Web</strong>.</p><p><strong>Product Teams</strong> — Designers and engineers building product features. They are the stakeholders and consumers of the design system.</p><h4>Ownership</h4><p>The diagram below outlines the main layers of our design system, indicating which teams are responsible for each part.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eosf_pfGa8mPyQOXNkYj9Q.png" /><figcaption>Design parts ownership</figcaption></figure><h3>Key pillars</h3><h4>Unified theme</h4><p>All Bolt products must share the same visual identity. When the branding team changes the accent colour or typography, it should be propagated across all apps quickly and safely, ideally without requiring any effort from the product teams.</p><p>There is no out-of-the-box solution for that. Front-end tech stacks are too different, so Bolt designers and engineers built a solution that handles all cases and works seamlessly with our internal tools.</p><p><strong>Our approach:</strong></p><ul><li><strong>A centralised theme repository</strong> (JSON-based), owned by the <em>Design System team</em>. As mentioned, there are only designers, but very special ones. They can define component APIs, support JSONs, and even review platform-specific code in some cases.</li><li><strong>Theme export script,</strong> owned by the <em>Platform team</em>s<strong> </strong>to convert the unified JSON to native formats (Android XML, iOS assets, React Native styles, etc)</li><li><strong>Theme export pipeline </strong>that runs the export script automatically (daily or on demand) and delivers the result to the particular repositories. In the case of Android, it runs nightly and opens a PR to the UIKit library if there are any changes.</li></ul><p>The theme is the foundation of the design system. Our theme repository is called `design token`, which reflects its fundamental role. It’s a smart structure that balances flexibility with consistency. Building and maintaining such a solution is a complex technical challenge in its own right.</p><h4>Design pragmatism</h4><p>Design should not only look good — it must be implementable with minimum effort.<br>We deliver quickly, so designers need to understand which UI components already exist, which customisations are safe, and which would require more extensive engineering changes.</p><p><strong>Our approach:</strong></p><p>We create a comprehensive specification of our UI Kit in Figma, along with a set of implementations for all frontend platforms that we require.</p><p><strong>The UI Kit in Figma </strong>contains</p><ul><li><strong>Component anatomy</strong> — internal structure of the component to be considered by the platform engineers while implementing.</li><li><strong>API specification</strong> — parameters that are accessible for the designers and should be supported in the codebase.</li><li><strong>Accessibility guidelines</strong> — screen reader instructions, focus and so on, to comply with accessibility requirements.</li><li><strong>Usage guidelines</strong> — semantics and best practices for the product designers.</li><li><strong>Figma components</strong> themselves and the variants matching the spec as much as possible</li><li><strong>Implementation status</strong> per platform — some components may not yet be implemented for certain platforms, and product teams should consider this when planning features.</li></ul><p><strong>UI Kit in codebases</strong> — UI components implementation, matching the Figma specification described above. Every UI kit is located in a separate repository and owned by the specific <em>Platform team</em> (Mobile, React Native or Web)</p><p>Having clear specifications and implementation statuses ensures that all teams speak the same language — designers understand the engineering progress, and engineers can easily interpret product designs.</p><h4>Backend-driven UI</h4><p>As some of our mobile applications are developed for native Android/iOS, they may exhibit misalignments in appearance and behaviour. To reduce this gap — and to accelerate feature delivery — we’re experimenting with a backend-driven UI approach, where the backend defines parts of the interface (or even entire flows).</p><p>Our solution is purely engineering-led and has no design ownership, but it is still based on the same design tokens and specifications provided by the <em>Design System</em> team.</p><p><strong>Our approach</strong></p><ul><li><strong>Common UI model</strong> — We reuse the same components defined in the design system, so the natural thing is also to use the same network models when data comes from the backend. Sounds easier than it goes, but we make progress.</li><li><strong>Backend-driven layouts</strong> — Some screens are rendered directly from backend JSON. Clients support a small set of containers (such as vertical or horizontal stacks) and dynamically place UI elements.</li><li><strong>XML-like markup</strong> — Even before backend-driven layouts, our backend sent formatted text. We built a custom tag converter that applies colours and text styles aligned with the design system.</li></ul><p>Building a flexible backend-driven UI is a challenge that could easily fill a separate article. Its success relies on a solid foundation — precise specifications and well-designed UI components. That’s also why our Figma specs look so technical: they are designed to speak backend language.</p><h3>Adoption</h3><p>Even if a technical solution is built, it doesn’t mean it will be used.</p><p>We have dozens of product teams for different kinds of frontend, with designers and engineers, having their own projects, priorities, deadlines and established habits. Getting everyone to switch to a shared design system isn’t just a technical migration — it’s a cultural shift, so it requires advocacy across all roles involved in product development.</p><h4>Design side</h4><p>Product designers need onboarding to the design system. Sounds not intuitive, but the UI Kit in Figma is a framework that has its learning curve.</p><p>What do we do:<br><em>Design system team</em> approaches the product designer to advocate the best practices through:</p><ul><li>Onboarding sessions</li><li>Recurring meetings with product design teams</li><li>Qualitative research initiatives to get feedback from the product teams and adjust the components according to the needs of the business</li></ul><p><em>Product engineers</em> often notice incorrect components or colour usages in the feature design and ask the designer to fix it.</p><p>Unfortunately, there’s no CI to find the mistakes in the product design automatically.<strong> </strong>Educating is essential.</p><h4>Engineering side</h4><p><em>Platform teams</em> own the theme export and shared UI components, but are not involved in the feature development.</p><p>What did we do in the Mobile platform team (and I personally as Android platform engineer):</p><ul><li><strong>Technical meetups</strong> — Periodical sessions to explain how things work and advocate the design system usage.</li><li><strong>Pipeline checks</strong> — Automated CI checks for usage of legacy components, colours or styles. If new violations are found, the Platform team is automatically assigned to such PRs, so they can review and suggest better solutions.</li></ul><p><strong>IDE tools</strong> — Inspections in Android Studio to suggest migrating old patterns to the new ones. Bulk migration and AI are prone to errors, and manual migration is time-consuming. Inspection is a balanced solution: the quick fix suggests a correct migration, which can be done in bulk, but remains semi-manual and can be applied step by step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-wlpdGkhubEI8Ub4.png" /><figcaption><em>Android Studio inspection suggests to migrate to new component matching text style</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_giLetW6x_Yls2Fx.png" /><figcaption><em>Android Studio inspection found incorrect color usage and suggests auto-replacement</em></figcaption></figure><h3>Conclusion</h3><p>What benefit we got from the design system so far:</p><ul><li><strong>Faster and centralised updates</strong><br>Recently, we were asked to change all accent colours across our applications to a new shade of green. Thanks to the Design System, this happened automatically — no manual work from product teams was required. Updating the values in one place and running the theme generation scripts was enough to propagate the change everywhere.</li><li><strong>Dark mode support</strong><br>Several of our apps now support dark mode. The unified theme already includes both light and dark variations, so as long as teams use the theme colours correctly, their products automatically adapt to both modes with minimal effort.</li><li><strong>Improved accessibility</strong><br>We’ve resolved many accessibility issues around contrast and readability. In the past, we lacked clear ownership and a process for this, which caused recurring problems during app reviews. The Design System now handles many of these tasks out of the box, ensuring accessible defaults across all products.</li><li><strong>Fewer inconsistencies and reworks</strong><br>The Design System helps prevent common issues that used to slow us down — like minor, one-off design tweaks that required extra engineering effort or introduced subtle bugs. With shared components and precise specifications, designers avoid making conflicting customisations, and engineers no longer need to fork or override components. As a result, we reduce duplicated work and maintain a consistent UI across our products.</li><li><strong>Easier cross-team collaboration.</strong><br>Designers can now move between teams and verticals with little onboarding — the shared system means consistent tools, patterns, and terminology. For frontend engineers, switching teams still requires learning a new tech stack, but at least the design layer is familiar, and product Figma files no longer need extra explanation.</li></ul><p>Building a cross-platform Design System for a large company is a real technical challenge that needs strong engineering skills and strategic vision from the design side. However, it is more than a technical solution — it’s an integral part of a company’s culture of design and development. Building this culture takes time, communication, proper organisation and persistence.</p><p>We’ve made significant progress, but the journey continues, and challenges remain.</p><h3>Join us!</h3><p>Grow fast, make a global impact, and help make cities for people, not cars. Explore hundreds of open roles <a href="https://https//bolt.eu/en/careers/">on our careers page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2674bb314787" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bolt-labs/building-a-cross-platform-design-system-2674bb314787">Building a cross-platform design system</a> was originally published in <a href="https://medium.com/bolt-labs">Bolt Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>