.webp)
Recruitment & Business Software
Building Flutter UI From Figma With AI
Less UI Implementation Time
Design Revision Rounds per Screen
Critical UI Defects at Release
From Implementation to Approved PR
What Is the Recruitment Platform?
The project involves a Flutter mobile application in the recruitment sector, alongside supporting web services.
Aetherius contributed to feature development, bug fixing, and UI implementation within the existing product. Our engineer used Cursor and Claude Code to explore the codebase and generate changes, with Figma MCP providing design information and Jira MCP supplying task context.
Generated implementations were reviewed, corrected where necessary, and checked in the application before peer review. The client and product name are confidential.
Challenges and Solutions
Implementing new screens required translating Figma designs into Flutter code while following the project’s existing conventions. AI-generated layouts could misinterpret design attributes or introduce unnecessary widgets, leaving differences between the first implementation and the intended design.
Our engineer used Figma MCP to give the coding agent access to relevant design information, including colors, typography, and dimensions. The generated UI provided a starting point, which the engineer reviewed against the design, corrected, and simplified before acceptance.
Feature development and bug fixing required an understanding of both the ticket and the existing codebase. Design information alone did not explain expected behavior, edge cases, or dependencies on other functionality.
Jira MCP provided access to task details, while project instructions and feature-specific documentation guided the agent toward relevant code and implementation conventions. Before implementation, our engineer worked through requirements and a plan with the agent, clarifying questions and dependencies where needed.
An initial implementation could look close to the design while still requiring structural or behavioral corrections. Generated tests also needed checking against the actual requirements rather than acceptance based only on passing results.
Our engineer reviewed the diff, corrected layout differences, simplified widget structures, and checked application behavior. The workflow included relevant tests, manual checks, and peer review before merge, with particular attention to native integrations where applicable.
.svg)
.png)
What Partner Said About Our Work
“I liked that they looked beyond whether a screen matched the design and paid attention to how the code was structured. They simplified generated components where needed, which mattered to us because our team would continue working on those screens.”
What Keeps
the Project Running
Other Projects We’ve
Worked On
.svg){kind=icon}
Tell us about your project
You’re one step away from getting the right developers.
"Aetherius' work achieved the correct functionality, satisfying the client's expectations, and planning to collaborate on a larger project in the future."
