mobile

In my previous post I showed how to introduce search as type behavior into Xamarin.Forms app with standard Forms Behaviors.

Search as type functionality is quite often seen on the web as well as in mobile apps. Let’s see how to make it work in Xamarin.

Detecting on-screen keyboard toggles and proper handling of such changes can be quite tricky. Android tries to deal with those events on its own but its behavior is often far from perfect.

Today’s mobile apps are rarely created as text-only. Most of them needs at least in-app icons for toolbars. In many cases you can find graphics for mobile platforms as ready to use resources on the Internet, i.

It’s very common to have multiple versions of the app during development - i.e. stable beta and store/production or alpha that contains the latest changes.

In last post I described how to cope, in some extent, with different pace of delivering mobile app versus it’s supporting backend.

Modern mobile apps are rarely developed as offline-only. They typically communicate with backend services that feed them with data, keeps in sync with their web equivalents or allows for various external integrations.

XAML compilation is (or at least should be) one of the default optimisation steps in Xamarin.Forms app development. It really speeds up the app especially on Android.

Standard Xamarin.Forms Xamarin.Forms.Editor control offers edit capabilities similar to Entry but for multiline text. Unfortunately unlike Entry it doesn’t support displaying placeholder text out of the box.

Most of iPhone and iPad users can easily recognize icon badges - the pattern for application notifications typically presented in app icon or navigation bar.