• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Xamarin in Action: Creating native cross-platform mobile apps: Entry Barriers?

 
Bartender
Posts: 1868
81
Android IntelliJ IDE MySQL Database Chrome Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Jim Bennett,

it's great that you have decided to stop by and allow us to pick your brain regarding Xamarin.

What would you say is that most common entry barriers for Java/Android developers when looking at using Xamarin?
How would you suggest people overcome those barriers?
 
Author
Posts: 12
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The biggest barriers are:

Tooling

Lots of moving pieces are involved with mobile apps - Xcode and the various SDKs and tooling on iOS including the provisions profiles, the Android SDKs and tools for Android. It gets a pain, and adding Xamarin as well can cause a few issues. Microsoft are working to smooth these out, but the top tip is to follow the docs when installing and configuring and always uses the latest bits!

Running on emulators and devices
This isn't a Xamarin specific thing, but mobile in general is a pain. Provisioning profiles on iOS to run on devices, Android emulators which didn't run on AMD chips or Hyper-V until recently. Again, follow the docs carefully and if you want to run Android emulators and have an AMD chip or Hyper-V for things like Docker, give the preview version a go (https://aka.ms/AA1v77v).

Architecture
Jumping from native to Xamarin has a mental leap around architecture. If you've built iOS and Android in the past, you would have built an app twice. With Xamarin you try to maximise the amount of shared code, which means a different way of thinking, pushing as much as possible into shared code. THat's where Xamarin in Action comes in, it covers how to use MVVM to maximise code re-use. So how to overcome? Buy my book!
 
Pete Letkeman
Bartender
Posts: 1868
81
Android IntelliJ IDE MySQL Database Chrome Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for you valuable input. I can see iOS/Mac hardware being an issue.
 
JimBob Bennett
Author
Posts: 12
5
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Pete Letkeman wrote:Thanks for you valuable input. I can see iOS/Mac hardware being an issue.



That is one issue I guess - if you want to develop for iOS you HAVE to have a Mac. Apples rules. Though you can rent build servers in the cloud from people like MacInCloud. It's slower but a great way to get started without paying for a Mac.
 
Always look on the bright side of life. At least this ad is really tiny:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic