Figma to MAUI UI Development for Ipad Pro

## .NET MAUI Developer – Convert Figma Designs to Functional MAUI UI We are looking for an experienced **.NET MAUI developer** to take completed Figma designs and implement them as working .NET MAUI screens. This is not a design project. The UI/UX has already been created by a designer in Figma. Your job is to accurately translate those designs into clean, maintainable .NET MAUI code. ### Scope We will provide: * Figma designs/screens * SVG assets exported from Figma * Existing .NET MAUI project/repository * Direction on the expected navigation between screens You will: * Recreate the provided Figma screens in .NET MAUI * Convert and organize the provided SVG assets for proper use within MAUI * Place assets in the appropriate MAUI resource structure * Implement fonts, icons, colors, spacing, sizing, and other shared resources correctly * Create reusable styles/resources rather than duplicating styling throughout the application * Make the navigation elements clickable and functional * Implement navigation between the screens included in the Figma design * Maintain close visual fidelity to the supplied Figma files * Make the layouts work properly across the target iPad/iOS resolutions * Integrate the work into the existing MAUI project without breaking existing functionality ### Navigation The application does **not** need backend functionality as part of this project. However, the UI should behave like a working prototype. For example: Dashboard → Customer → Application → Details → Back Buttons, tabs, menus, cards, back buttons, and other navigation controls shown in Figma should navigate to the appropriate MAUI screen. The goal is to be able to run the application and click through the Figma-designed workflow. ### MAUI Resource Structure We expect the implementation to use normal .NET MAUI conventions, including appropriate use of: * `Resources/Images` * `Resources/Fonts` * `Resources/Styles` * `App.xaml` * Resource dictionaries * SVG/image resources * Reusable styles * Reusable controls/components where appropriate We do **not** want every screen implemented as a large amount of duplicated XAML. ### Technical Expectations Experience with: * .NET MAUI * C# * XAML * iOS/iPad development * Figma-to-code implementation * SVG assets in .NET MAUI * MAUI Shell/navigation or an equivalent clean navigation architecture * Responsive/adaptive MAUI layouts * Git/GitHub Experience building production-quality MAUI applications is strongly preferred. ### Deliverables 1. Completed MAUI implementation of the supplied Figma screens. 2. All supplied SVG/image assets correctly incorporated into the MAUI project. 3. Shared colors, fonts, styles, and UI resources organized appropriately. 4. Working navigation between screens. 5. Project successfully builds and runs. 6. Source code committed through Git. 7. Brief documentation describing any reusable components/resources created. ### Definition of Done A screen is considered complete when: * It closely matches the Figma design. * Images/icons render correctly. * Fonts, colors, margins, padding, and sizing are reasonably faithful to Figma. * Navigation elements work. * There are no obvious layout issues. * The application compiles without errors. * The implementation follows reasonable MAUI/XAML development practices. ### When Applying Please include: 1. Examples of .NET MAUI applications you have personally developed. 2. Examples of Figma designs you have converted into MAUI/XAML, if available. 3. Your experience working with SVG assets in MAUI. 4. Your experience developing specifically for iPad/iOS using MAUI. 5. Whether you recommend MAUI Shell navigation or another navigation approach for this project, and why. 6. Your GitHub profile or examples of relevant source code if available. **Please begin your response with the words `MAUI FIGMA` so we know you read the complete posting.** ### Initial Milestone We would like to start with **one representative Figma screen plus its navigation**. The first milestone will be used to evaluate: * Visual accuracy * XAML/code quality * Resource organization * Navigation * Communication * Ability to work within our existing MAUI application If the first milestone is successful, we expect to award the remaining screens to the same developer.