The ordinary process of building and shipping an (iOS) app often includes at least two builds: The first for your internal tests, the second for the public (AppStore). That's somewhat less than perfect and we can do better.
I am looking for our sixth team member who will work with us on a large iOS app and other cross-platform apps for both iOS and Android. Location: Munich, working 100% remote is possible. Interested? Read on.
When digging around Xamarin.Forms over the past holidays I almost accidentally created a new MVVM Framework. Here is the story behind.
Xamarin.Forms provides cross-platform messaging capabilities for Android, iOS and Windows Phone with its MessagingCenter – but in a really strange fashion. I thought there must be a simpler way.
Everyone who has already built and shipped an iOS app to the AppStore knows the pain. That awful feeling when dealing with provisioning profiles, development and distribution certificates.
Three weeks ago the (probably) first official Developer Walk took place in Dresden, the lovely capital of Saxony in Germany – an event that should and will be repeated.
Six months ago I made a serious mistake: I replaced my beloved MacBook Air with a MacBook Pro. In the period that followed I tried to be strong, but eventually I gave up last week. Now I am running my best hardware setup ever.
I'm not a guy you are likely to meet at a classical tech conference. I don't like to waste my time with marketing bullshit and presentations of unprepared speakers. But I do like to meet like-minded people, good conversations, and some Schnitzel and beer.
One of the rather annoying things of developing native iOS apps has always been a relatively common task: Displaying data with a varying size in UITableViews. Since iOS 8 it is easier than ever before – once you know the trick.
Some features of your app may only be useful if the device of your user is currently connected to the internet, so you can make API calls, load images or do some other stuff.