Refresh WPF Form application Input UX
Budget: $750 – $1,500 USD
Our in-house WPF desktop application performs well functionally, yet the way users complete its many forms feels dated and cumbersome. I want to rework those interactions so every field, dropdown, and dialog feels light, self-explanatory, and instantly validates what the user is doing. Visual polish is welcome, but the core goal is to simplify the input flow and bake in solid client-side validation that prevents errors before they hit the backend.
You’ll start by reviewing the existing XAML screens (I’ll provide the repo and a short Loom walkthrough). From there, I’m expecting wireframes or an interactive prototype—Figma, Adobe XD, or Blend for Visual Studio all work—demonstrating:
• A trimmed number of steps or clicks for each form
• Clear inline validation messages and constraint hints
• Consistent focus states, error states, and success confirmations
Once the interaction model is approved, translate it into reusable WPF resources: styles, control templates, and light theme/dark theme resource dictionaries so my dev team can drop them in with minimal refactoring. Please keep your solution .NET 6 compatible and stick to native WPF controls unless a third-party control meaningfully improves the experience.
Acceptance will be based on:
• Prototype walkthrough showing the simplified flow and validation logic
• Delivered XAML styles/resources that compile cleanly in our staging branch
• A short hand-off guide explaining naming conventions and extension points
If you’ve modernized legacy WPF UIs before—especially high-form apps—let me know and share a couple of screenshots or a short demo link.
You’ll start by reviewing the existing XAML screens (I’ll provide the repo and a short Loom walkthrough). From there, I’m expecting wireframes or an interactive prototype—Figma, Adobe XD, or Blend for Visual Studio all work—demonstrating:
• A trimmed number of steps or clicks for each form
• Clear inline validation messages and constraint hints
• Consistent focus states, error states, and success confirmations
Once the interaction model is approved, translate it into reusable WPF resources: styles, control templates, and light theme/dark theme resource dictionaries so my dev team can drop them in with minimal refactoring. Please keep your solution .NET 6 compatible and stick to native WPF controls unless a third-party control meaningfully improves the experience.
Acceptance will be based on:
• Prototype walkthrough showing the simplified flow and validation logic
• Delivered XAML styles/resources that compile cleanly in our staging branch
• A short hand-off guide explaining naming conventions and extension points
If you’ve modernized legacy WPF UIs before—especially high-form apps—let me know and share a couple of screenshots or a short demo link.
Related categories:
.NET
C# Programming
AutoCAD
WPF
XAML
Prototyping
Figma
Adobe XD
Visual Design
User Experience Research