Carol Zambon

Shaun, About your concern regarding the code-behind, I know that there are some static methods on class `Device` that people uses when attempting to return markup values, such as `OnPlatform`...

Ok, I just implemented a static class (`Markup`) which behaves just like `Device.OnPlatform` (which I know it is obsolete on Xamarin, but on Xamarin it was replaced by RuntimePlatform which...

Hello @pictos, Here are my answers regarding the questions/issues you raised previously. > [Here](https://github.com/carolzbnbr/OnScreenSizeMarkup/blob/3f39f23e4197eb22a9bf7904023093ca1d04c54d/src/OnScreenSizeMarkup/OnScreenSizeMarkup.Core/DefaultCategoryFallbackHandler.cs#L12-L16) you cache a bunch of device models and their Screen category (Small, Large, Medium, etc). And...

Hi @pictos, Hope you are doing great. > > By now, my main concern is related on the screen categorization versus it's size, how to make it less "hard coded"...

Hi @bijington, hope you are doing great! > > Ok, I just implemented a static class (`Markup`) which behaves just like `Device.OnPlatform` (which I know it is obsolete on Xamarin,...

Hi @VladislavAntonyuk thanks for the info. > As for default values, I propose such options: https://mudblazor.com/features/breakpoints#breakpoints This approach has some drawbacks: 1 - It is pixel-based, instead of "dp", or...

Hello @brminnick, > * How do we set default values? Should we have different defaults for Mobile vs Desktop? > * Are the values overridable? We can change my implementation...

Removed, duplicate

Hi @bijington, > Sorry I missed that this would be C# only. No problem at all. :D > I guess this `IMarkupExtension` implementation for C# could use the underlying `IMarkupExtension`...

Hi @VladislavAntonyuk thanks for reviewing my PR. I wrote some responses on some of your suggestions. If you still find something does not make sense, let me know.