Replies: 16 comments 2 replies
-
|
Most of the times, I first look at the design in Figma or whatever the designer shares. I break it into small components like buttons, cards, sections etc. and then start building the layout first. |
Beta Was this translation helpful? Give feedback.
-
|
To "rise" in the GitHub community with this discussion, it’s best to frame it around the modern handoff and development cycle of 2026, where the lines between design and code (like "Design-to-Code" AI tools) are blurring. Here is a high-quality, professional draft for your GitHub Discussion: Title: Beyond the Handoff: Modern UI Development and Designer Collaboration in 2026 As the ecosystem shifts toward more automated design-to-code workflows and AI-assisted UI generation, I’m interested in how your day-to-day collaboration with designers has evolved. Whether you are building with React/Next.js, Vue, or Svelte, the "handoff" is no longer a single event but a continuous loop. I’d love to hear your insights on two specific areas:
AI Integration: How are you using GitHub Copilot or v0 to interpret design tokens? Do you find it more efficient to have AI generate the initial structure from a screenshot, or do you prefer hand-coding for better accessibility/semantic HTML?
The "Grey Area": How do you handle animations (like GSAP or Framer Motion) that are often hard to capture in static designs? Do you pair-program with designers, or do you use a "motion spec" tool? GitHub for Design: Does your design team participate in GitHub Discussions or Pull Request reviews to verify UI accuracy, or do you keep feedback strictly in design tools? What I'm currently doing: Looking forward to hearing about the tools and "soft skills" that make your frontend life easier! |
Beta Was this translation helpful? Give feedback.
-
How I Usually Develop UI and Work With DesignersHi! Front-end developer here 👋 My UI development workflow usually looks like this: 1. Understanding the Design
If something is unclear, I ask the designer early before coding. 2. Breaking the UI Into Components
This makes the UI scalable and easier to maintain. 3. Design System / Tokens
Then I map them into CSS variables or a system like Tailwind config. This keeps the UI consistent across the project. 4. Implementing Responsiveness
I test across different screen sizes while developing. 5. Communication With Designers
Typical questions I ask designers:
6. Iteration
In short: This process helps keep the UI consistent and collaboration smooth. Curious to hear how other front-end developers approach this as well! |
Beta Was this translation helpful? Give feedback.
-
|
The first most important thing is to visualize your idea in figma mate. You sketch the design using buttons, shapes and patterns and more. You can also test the UX on figma to improve user experience then only need to code the visual. For the second question, its always better to talk directly to your co-dev on zoom or microsoft team (i personally use this) about the idea first. You guys work on each branch in vscode and make pull req on github with at least 2 people to review the code. Thats it, hope it helps you mate. Have a good one |
Beta Was this translation helpful? Give feedback.
-
|
Ok, so I will answer both of your questions shortly and sweetly,
At least that's how I do it, and it helps. |
Beta Was this translation helpful? Give feedback.
-
I typically start by reviewing the design specifications (Figma, mockups, or design system guidelines) to understand layout, spacing, typography, and component behavior. Then I break the UI into reusable components and build them step-by-step. I focus on responsiveness, accessibility, and keeping the code clean and maintainable. I also test the UI across different screen sizes and browsers to ensure consistency. How I communicate with designers: Overall, clear documentation, quick feedback, and collaboration between developers and designers make the UI development process much smoother. |
Beta Was this translation helpful? Give feedback.
-
|
I generally use CSS and JS quite a bit, it's a good combination, but Tailwand is full of great features, and I also use LinkedIn for conversations. |
Beta Was this translation helpful? Give feedback.
-
First I understand: what the feature should do user flow business requirements responsive behavior (mobile / tablet / desktop) Usually this comes from: product manager designer task in Jira / Trello / GitHub
Designs usually come from tools like: Figma Adobe XD Sketch From the design I check: spacing colors typography responsive layouts components |
Beta Was this translation helpful? Give feedback.
-
|
I usually build UI by turning design mockups into code with HTML, CSS, and JS frameworks like React. For designers, I use Figma comments, Zeplin, or chat to clarify spacing, colors, and animations, making sure the design works well in the app. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Developing UI
|
Beta Was this translation helpful? Give feedback.
-
|
We build reusable components (like buttons or navbars) using a "Component-Driven" approach.
We use Figma as our shared "source of truth." |
Beta Was this translation helpful? Give feedback.
-
|
Hi, UI development usually depends on the project and the team workflow, but most front-end developers follow a similar process. For UI development, we typically start with the design files provided by designers (often from tools like Figma, Adobe XD, or Sketch). From there, we break the design into reusable components and implement them using HTML, CSS, and JavaScript frameworks such as React, Vue, or Angular. Many developers also use component-based design systems, CSS frameworks, or UI libraries to maintain consistency and speed up development. Communication with designers is very important. Usually, we collaborate through design tools where developers can inspect spacing, colors, and typography directly from the design file. We also discuss edge cases, responsive behavior, animations, and user interactions. Communication often happens through tools like Slack, Jira, or project meetings where both developers and designers clarify requirements and review feedback. Regular feedback loops, design reviews, and shared style guides help ensure that the final UI matches the design while remaining technically feasible and maintainable. |
Beta Was this translation helpful? Give feedback.
-
|
For most frontend work, the UI development process usually follows a few steps.
In practice, the best workflow is when designers and developers collaborate early so that the UI is both visually correct and technically practical to implement. |
Beta Was this translation helpful? Give feedback.
-
|
For UI development, I usually start by breaking down the design into components—buttons, forms, cards, etc.—and then build them in a modular way so they’re reusable. I often use frameworks like React, Vue, or plain HTML/CSS depending on the project. For styling, I rely on CSS modules, Tailwind, or styled-components to keep things organized. When working with designers, communication is key. I review design mockups carefully, ask for clarifications on spacing, colors, and interactions, and use tools like Figma, Zeplin, or design handoff plugins to make sure the implementation matches their vision. Frequent check-ins and sharing progress early helps avoid surprises. |
Beta Was this translation helpful? Give feedback.
-
|
Hi mini0192 As a front-end developer, I usually start by reviewing the design files provided by the design team (mostly in tools like Figma). I break the UI into small reusable components and then implement them using HTML, CSS, and JavaScript or a framework like React/Vue/Angular. I also make sure the UI is responsive and works well across different screen sizes and browsers. For communication with designers, we typically collaborate through tools like Figma where I can inspect spacing, colors, typography, and download assets. If something is unclear (for example interactions, responsive behavior, or edge cases), I usually ask questions directly in the design comments or discuss it with the designer through Slack or meetings. Good communication between developers and designers helps ensure the final UI matches the design and provides a good user experience. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Hi everyone
i have questions for Front end programmers
How do you usually develop ui?
How do you usually communicate with designers?
Beta Was this translation helpful? Give feedback.
All reactions