Langsung ke konten utama

Hands on Xamarin Platform Pipeline - Introduction


Quality in mobile industry is becoming nowadays something mandatory. Also mobile users are known to be very demanding at the point only 16% of users keep an app after 2 buggy experiences.

Also, studies shown that mobile users use between 5-20 max applications, currently the mobile store size is about 3 billion applications per platform. So how can a developer deliver an application and be on the top 10? This requires of course strong platform and high quality tools.

For those who doesn’t know Xamarin, following a quick information about it:

  • Founded in May 2011, acquired by Microsoft in February 2016
  • Supports Native iOS, Android, Mac and Windows Mobile App development platform
  • Supports C# 6 as development language, initially based on Mono
  • Has same day support and always up to date
  • Application built on Xamarin have native characteristics: Native User Interface, Full SDK Access and Native Performance
And of course, we can’t forget the famous Xamarin quote: “Anything you can do natively you should be able to do with Xamarin.”

Using Xamarin since 2013 and being a user of other mobile development approaches (Native development using Android Java, iOS Objective-c or Swift, hybride architectures with Ionic...), in my point of view Xamarin is the best choice that helps deliver high quality cross platform mobile applications.
Xamarin currently covers the complete DevOps pipeline:


In the following blog posts I expect to give a practical guidance and tutorials in order to have a mobile application that uses all the Xamarin tools and to have Continuous integration and Continuous Delivery in place.

We'll start by Context & Environment Description then the Develop-Test-Build-Distribute-Monitor plan will be followed.

Develop

Let's start by an offline application
Add authentication using Azure Active Directory
Let's explore some nice features of Xamarin Studio 6
Exploring Visual Studio Mobile Center
Add Facebook authentication

Build

Komentar

Postingan populer dari blog ini

Android Tutorial: Use LeakCanary to detect memory leaks

Overview The memory leak can be a headache to detect and to resolve, small memory leaks can be hidden and may be seen after a long usage of the application and hunting memory leaks is not a simple task. In this tutorial we will create a leaked application and we will use the LeakCanary library to detect the memory leak. Step 1: add the LeakCanary dependency to the application Modify the app/build.gradle to add the LeakCanary dependency as follows: Step 2: Extend and configure the Application class We need to call LeakCanary.install in onCreate method: Step 3: Create a leaked activity For this we will create a singleton class that saves the context: Then, the main activity (leaked one), will use the singleton and then we'll go to a new activity: Then, in the new activity we'll call System.gc to force the garbage collector in order to accelerate the analysis. Step 4: Retrieve the analysis result A nice notification can be shown: The result can be retrieved from logcat: Source c...

QR-Code Generator - Library

In this Post, I introduce my new Gradle Library. This Library is used to Generate QR Code Automatically for our specified input. How to Import the Library: Gradle: compile 'androidmads.library.qrgenearator:QRGenearator:1.0.0' Permission: <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> How to use this Library: After importing this library, use the following lines to use this library. The following lines are used to generated the QR Code // Initializing the QR Encoder with your value to be encoded, type you required and Dimension QRGEncoder qrgEncoder = new QRGEncoder(inputValue, null, QRGContents.Type.TEXT, smallerDimension); try { // Getting QR-Code as Bitmap bitmap = qrgEncoder.encodeAsBitmap(); // Setting Bitmap to ImageView qrImage.setImageBitmap(bitmap); } catch (WriterException e) { Log.v(TAG, e.toString()); } Save QR Code as Image // Save with location, value, bitmap returned and type of Image(JPG/PNG). QRGSaver.save(s...

FlatBuffers Android Tutorial

FlatBuffers is an efficient cross platform serialization library for C++, Java, C#, Go, Python and JavaScript. It was originally created at Google for game development and other performance-critical applications. FlatBuffers is Open Source (Apache license V2) and available on GitHub . It's currently used by:   Cocos2d-x , the open source mobile game engine and used to serialize the game data. Facebook uses it for client-server communication in the Android app (see the article) . Fun Propulsion Labs at Google in most of libraries and games. Solution overview  The schema will be defind in JSON format, then it will be converted to FlatBuffer format outside the application The Java classes of the Data model will be generated manually using flatc (FlatBuffer compiler) Step 1: Build FlatBuffers Download the source code in Google’s flatbuffers repository .  The build process is described on Google's documentation FlatBuffers Building .  On MacOS for example: Open the ...