YES ! I am Xamarin Certified Mobile Developer! 🎉🙌🎉
This was really a great journey for me, a lot of new stuff learned. I need to say thanks to all great Xamarin University lecturers about the great content.

so, its almost 2018 and Xamarin.Forms still doesn't support RTL..

really, really xamarin guys?

Xamarin.forms. True multiplatform* by Microsoft.

*you just have to make sure not to use any of the platform specific features, or write 3 completely different codes

Create this fucking account just to say: FUCK XAMARIN!

Mono is great on Linux, but Xamarin.Android is a GAY RETARD!

Fucking Xamarin.Android apps are retarded, wait for them 3 fucking seconds and a simple Hello World app doesn't start.

Retarded Xamarin.Forms make the whole pile of shit a lot worse using fucking abstractions and stuff. And the geniuses at Uno Platform does not make this shit any better.

Why don't those nerds at Xamarin make a way to compile all C# code to native JVM bytecode and provide all C# core libraries AS NATIVE JAVA LIBRARIES, RATHER THAN LOADING A NEW USELESS RETARDED VIRTUAL MACHINE ON THE JVM?

So that's it. Guess there's no way to write good Android apps using C#.

Xamarin.Forms be like

Carousel Page is depreciated and will be removed soon. Use Carousel View.

Carousel View was removed from stable release channel because we felt it was ready.

...really guys

I loved you Xamarin.Forms I really did.
I defended you everywhere... Released 5 apps.

You FUCKING SUCK, no svg support (no none of the apis work), startup time is FUCKING insane, i could go on for hours......

Please any Android Developer out there is there any smooth transition to native? (Dont tell me about Js bullshit)

Help me fell the Native Power of Android.

Show me that apps don't need 20 seconds to start.

Working on a cross platform mobile app for work. We've decided to use Xamarin.Forms. Anyone else using this?

Fuck Xamarin! Fuck Xamarin.Forms!

It's slow, it's full of bugs, it's missing basic functionality, it's rapid new updates breaking older frameworks, it's a shitty unstable IDE on both Mac and Windows, it's the need to frequently reopen files or restart the IDE to fix "intellisense" or the false compile errors, it's non working UI builder and previewer, it's connection issues with simulators, emulators and real devices, ...

Have I forgotten something? Probably yes.

Your dev customer for many years.

Visual Studio Freaking 2017 and still no freaking XAML intellisense for freaking Xamarin.

Freaking spent more than one hour searching for a freaking fix in vain. Might as well have used that freaking hour and learn the whole freaking Xamarin.Forms XAML vocabulary. This shit sucks.

Xamarin.Forms sucks ass. Piece of garbage. If you wanna make a big project better not choose Xamarin.Form, trust me.

This is a continuation of my previous rant about admob being not very informative when it comes to invalid traffic and the resulting restriction in ad delivery.

I then wanted to use admob mediation to hang in facebook ads. My app is written with Xamarin.Forms.

So first I needed to make some facebook configuration - create an account, let my app review, create some ad placements and other shit. I came to the point where I had to put in a link to my privacy policy and the link could not be accepted due to some SSL fuckup -.-'

I then found out that there is an issue with my SSL Chain. With the help of whatsmychaincert.com I solved that issue. Little side note here: I have limited knowledge of that stuff and my cousin helped me set up my homepage so I had no idea what I was doing. Did a snapshot and luckily I did not needed that as everything worked :)
This took me around half an hour just so I can paste the fucking link to activate my app in facebook developer portal.

After that I made the whole mediation configuration shit - not an issue as google documented this quite well but it took some time.

Now comes the shitty part. To use admob mediation you need adapters to the other ad network. I found a nuget package with exactly what I needed just to find out that it is outdated. So I pulled the repo and saw that this thing is an aar binding library. Never did that stuff so I read some docs again. Updated the package and consumed it in my app.

The google docs then said "Use this mediation test shit to check if you did everything correct before going prod" - aar binding nr. 2 (but I am now familiar with that :P). This thing then told me that facebook ads could not be loaded because the SDK version is outdated -.-' SDK version comes from another nuget package which is referenced by the first aar thingie. I tracked that thing back to a repo where I found out that they are indeed totally behind. So I downloaded the aar, made a binding lib and bound that to my first aar binding lib as that depends on this.

Put that all back in my app - tested mediation and fucking finally after 6 hours everything comes together! all lights are green and things work.

Sorry if this is not quite a rant but it was quite a journey and I just had to share it.

Learning to develop. I must choose:
1. UWP
2. Android
3. iOS
4. Xamarin.Forms
Please give me suggestion, thank you!