Overview & philosophy
Marco treats the UI layer as product infrastructure: components should be predictable, testable, and cheap to change when the business pivots. That means disciplined state boundaries, not clever one-offs that only the author can extend.
He has shipped admin consoles, customer portals, and companion mobile apps where the hardest problems were not pixels but consistency—the same validation rules on web and device, the same error semantics when the API flakes, the same “empty state” story when a new tenant has no data yet.
He prefers small, composable primitives with clear names over mega-components that become merge-conflict magnets. When performance matters, he measures: render counts, bundle size, and image delivery—not premature micro-optimization.
Where policy allows, assistive AI can speed first drafts of markup or test ideas—never a substitute for design partnership or WCAG judgment. He keeps customer-specific flows and branded copy out of unapproved tools when your security team says so.
“Marco asks the questions designers love—about edge states and focus order—before we build the wrong thing beautifully.” — Product designer, fintech admin (anonymized)
Technical depth
Where Marco spends depth time on modern .NET UI stacks—always aligned to your design system and API conventions.
Blazor (WASM & Server)
.NET MAUI
Accessibility & UX engineering
- Semantic HTML where applicable; ARIA where Blazor components need explicit roles.
- Keyboard paths through multi-step flows; focus management on dialogs and drawers.
- Contrast and motion preferences respected; reduced-motion variants when appropriate.
Tools & platforms (representative)
Representative project types
Categories of UI work Marco has delivered repeatedly—compare to your roadmap and design maturity.
Admin & operations consoles
Role-based navigation, dense data tables with filters, bulk actions, and export flows that stay usable on laptops.
Customer self-service
Multi-step wizards, document upload with progress, and resilient retry UX when networks fail mid-flight.
Companion mobile
Field workflows, offline-tolerant reads where feasible, and push notification hooks aligned with your backend events.
Engagement models
UI work benefits from visible milestones—demos stakeholders can click—not opaque “framework weeks.” Marco structures work accordingly.
| Model | Minimum | Best when… |
|---|---|---|
| Dedicated monthly | Often 3+ months | You are building or revamping a product surface with steady design partnership. |
| Milestone delivery | Per release train | Scope is a module or epic (e.g., onboarding revamp, settings area, mobile v2). |
| UI audit + fix sprint | 2–4 weeks | You have accessibility debt, inconsistent components, or performance regressions to clear. |
Screens, states, and API contracts mapped against design files; gaps flagged before build.
Each slice demoable in staging with feature flags for risky areas.
Smoke tests, keyboard walkthrough notes, and README for component library consumers.
Ways of working with your team
Design: Marco asks for interaction specs for validation, errors, and disabled states—not only happy paths. He proposes engineering trade-offs when a visual idea would tank performance or accessibility.
Backend: He prefers OpenAPI or hand-written DTOs that match what the UI truly needs—avoiding “mega objects” that encourage accidental coupling.
QA: He supplies repro steps, screen recordings for visual bugs, and stable test IDs where automation is a goal—not last-minute guesses.
Attach your component library link (if any), primary user journeys, and one “worst screen” example—Marco uses that to calibrate week one.
Fit, boundaries & quick answers
- • Want one C# story across web admin and companion mobile.
- • Value accessibility and resilient UI states.
- • Have evolving APIs and need UI that adapts without chaos.
- • Need a primary React/Vue owner (Marco can consume APIs, not lead that stack).
- • Project is static brochureware with no .NET UI runtime.
- • Expect broadcast motion design without a motion spec or timeline.
Can Marco work from our Figma library?
Yes—tokens, components, and naming conventions can be mirrored or wrapped in Blazor/MAUI primitives.
Does he write automated UI tests?
Where the team invests in harnesses: bUnit for components, Playwright for critical smoke paths—scoped to value.
Mobile: iOS, Android, or both?
Both via .NET MAUI unless you explicitly target one store first; store policies and device labs discussed up front.
How does Marco use AI (if we allow it)?
As assistive support for drafting and exploration—never autonomous “AI UI.” He validates behavior, accessibility, and brand fit himself, and follows your AI and data-handling policies for any external tooling.
Bring Marco into your product squad
Share Figma (or equivalent), user journeys, and timeline—we’ll confirm fit and propose a ramp plan.
If your organization restricts AI tools or external prompts, say so—we align workflows to your security and procurement rules.