Xamarin.Forms Design Framework medium.com

1

In my personal trip to leverage all those small problems I found in my day to day, there’s one which sistematically reappears: I’m about to start a new Xamarin.Forms project for X platforms — please note the plural — but just have its design for one of them. For instance: I want my app to target Android & iOS, but just have the Android design.

The reasons why this happen would give for a different thread but I feel them as an homogeneus mix of:

  • Xamarin.Forms’ missunderstood, or we didn’t explain it quite well: it’s felt like Flutter — it appeared! — when it’s not
  • We don’t want to increase the time and money by spending a few more days with the rest of designs, for one reason or another we don’t see its value

I’ve been thinking a lot on this and nowadays have a strong opinnion which proposes one possible exit:

Xamarin.Forms Design Framework

Most of the times, when I’m working with a Zeplin project for a Forms app, the first servers as a handful guide of margins/paddings, sizes and colors. It’s not so much whether the status bar has a particular background color, or the button has any tweak which makes it look different. Obviously, those are things which in the end need to be done, but aren’t at the top of value.

Imagine we had something like http://design.xamarin.com where our Designers could head on and learn without the first scroll what actually Xamarin.Forms’ all about. In their language.

After this, it could propose a Design Framework which would isolate from platform specifics and would concentrate on letting Designers express our apps in an agnostic way. A quick example to explain this: a button in such Framework would be a flat box with text inside: as a Developer, I can gather its width & height, its relative position to the parent view,

Report Story

Leave Your Comment