we are ditching xamarin. why?

29
We are ditching Xamarin. Why? NorApps AS & Konstantin Loginov

Upload: konstantin-loginov

Post on 13-Jan-2017

162 views

Category:

Engineering


0 download

TRANSCRIPT

Page 1: We are ditching Xamarin. Why?

We are ditching Xamarin. Why?NorApps AS & Konstantin Loginov

Page 2: We are ditching Xamarin. Why?

Konstantin Loginov

8 years in mobile development• Windows Mobile• webOS• Windows Phone• iOS• Android

[email protected]

Football & mobile applications fanatic

| NorApps AS

Page 3: We are ditching Xamarin. Why?

Small team of 5 (soon 6!) people from Bergen, Oslo and Guadalajara

FotMob is our main product

We love football (yes, it’s a pre-requirement)

Featured by Google & Apple

Page 4: We are ditching Xamarin. Why?

Xamarin is cool

Page 5: We are ditching Xamarin. Why?

I ❤ C#, I’m sure you too

Page 6: We are ditching Xamarin. Why?

Xamarin apps are fairly reliable and fast*

* Millions of our users can confirm!

Page 7: We are ditching Xamarin. Why?

Complete API coverageSame-day support for new releases

Page 8: We are ditching Xamarin. Why?

After all… It’s cross-platform!

Page 9: We are ditching Xamarin. Why?

Sounds like Xamarin is perfect… But?

But it’s not

Page 10: We are ditching Xamarin. Why?

FotMob

Page 11: We are ditching Xamarin. Why?

• Started as Android-first app – 2008• iOS (C#) – 2011• WP7 & Windows 8 (C#) – 2012

Very UI-intensive application

Page 12: We are ditching Xamarin. Why?

Xamarin

Page 13: We are ditching Xamarin. Why?

Extra layer between you and user

Page 14: We are ditching Xamarin. Why?

No cocoapods, JCenter, (almost) no StackOverflow, no hope

Page 15: We are ditching Xamarin. Why?

Bugs

... and other 300 (opened / confirmed “iOS” bugs); 5000+ bugs for all categories

Page 16: We are ditching Xamarin. Why?

Xamarin-apps are “heavy”

Page 17: We are ditching Xamarin. Why?

46.0 47.1 47.2Download size

48.0 MB* 50.1 MB 39.9 MB

Install size 73.3 MB 80.1 MB 69.6 MBFeatures watchOS 1.0 App

Today ExtensionUNNotificationContentExtensionUNNotificationServiceExtension

watchOS 1.0 AppToday Extension

UNNotificationContentExtensionUNNotificationServiceExtension

watchOS 3.0 AppToday Extension

Xamarin-writtenSwift-written * Device Type: iPhone 6s

Page 18: We are ditching Xamarin. Why?

Xamarin Studio*

* Visual Studio doesn’t sound like an ideal solution either

Page 19: We are ditching Xamarin. Why?

FotMob Build time: 1:30 minutes* * Top config MacBook Pro 15”

Page 20: We are ditching Xamarin. Why?

Microsoft

* Not only because I’ve been working there for 3.5 years

Page 21: We are ditching Xamarin. Why?

Acquisition is always a risk

Page 22: We are ditching Xamarin. Why?

Windows Phone is dead

Page 23: We are ditching Xamarin. Why?

Apple

Page 24: We are ditching Xamarin. Why?

– Can we be featured? – Sure, do you watchOS 2.0 support? – .... – And what about now? – Have you watched WWDC? Our new notifications are amazing! –

You don’t want this to happen. Trust me.

Page 25: We are ditching Xamarin. Why?

Same-day support != working product

Page 26: We are ditching Xamarin. Why?

Ok, so what’s the status now?

Page 27: We are ditching Xamarin. Why?

We have rewritten so far to Swift:• Apple Watch App• Today Extension• Notification Service Extension• Notification Content Extension• All data model & parsers & utils classes

We have released semi-Swift-version with support all new iOS 10 features and have been featured

Xamarin still does not support 3D-touch-notifications *

Core app will be rewritten and scheduled to be released in Q1 2017

* 24th of October

Page 28: We are ditching Xamarin. Why?

Don’t miss my next year’s talk “We ditched Xamarin. How did it go”

@klogi_norge

https://no.linkedin.com/in/klogi

[email protected]

Page 29: We are ditching Xamarin. Why?