Over a year ago, I wrote a quick tip on getting device Unique ID for Windows and Windows Phone (8 & 7). Lately, at RedBit, we have been doing quite a bit of iOS, Android and Windows projects using Xamarin and recently put two articles up on our learnings, Cross Platform Animations using Xamarin Forms and GZip Compression with Xamarin Forms. For different reasons, we needed to use a unique ID to identify devices and getting the device ID on each platform is obviously different.

For iOS you can use the UIDevice.CurrentDevice.IdentifierForVendor which can be called from a Xamarin iOS or Xamarin Forms app.

For Android, again it’s a different API but note, that you need API Level 9 or higher for this to work. It is called as follows from Xamarin Android or Xamarin Forms

For Windows you can reference this post I wrote a while back Getting Device ID on Windows & Windows Phone.

At RedBit we have an internal library that we use and here is an excerpt of our RedBit.Mobile.Hardware class

public string DeviceId { get { return GetDeviceIdInternal(); } } ///
/// Gets a device unique identifier depending on the platform ///

/// string representing the unique id private string GetDeviceIdInternal() { var id = default(string); #if __IOS__ id = UIKit.UIDevice.CurrentDevice.IdentifierForVendor.AsString(); #elif WINDOWS_PHONE id = Windows.Phone.System.Analytics.HostInformation.PublisherHostId; #else id = Android.OS.Build.Serial; #endif return id; } }

I’ve put a sample up on GitHub that outputs the device ID for iOS, Android and Windows. Here is the output on iOS.


As always, comments welcome!

In a recent project the RedBit team worked on, we decided to use Xamarin.Form to  build an app for Windows Phone, iOS and Android. Xamarin Forms is still a v1 product but the Xamarin team is rapidly releasing updates to fill in some gaps. As a developer you still have the opportunity to extend Xamarin Forms, for example by building custom renderers. We’ll have a series of blog posts on some learnings from the team to help extend Xamarin.Forms and meet our client’s requirements.

For this first post we’ll be looking at how to implement GZip Compression across iOS, Android and Windows. The benefit to using GZip is there is less data going over the wire reducing mobile data consumption. In the US it’s not much of a problem to send large amounts of data because of unlimited data plans, but in Canada (and other parts of the world) data is not so cheap. In terms of compression, here is a chart showing the difference in data size making a request to http://en.wikipedia.org/wiki/Gzip.

To read more about how to use GZip Compression with Xamarin Forms head over to the RedBit post to see the entire walkthrough.

test-cloud-logoCome join me March 12th where I will be presenting at the Toronto ALM Usergroup on how you can Test your iOS and Android apps on 1000+ devices.




Here is the session overview

Imagine that you’ve finished an app. You’ve tested on your physical device and all goes well.

You deploy. It doesn’t go well. Someone tests on a device you don’t have. It crashes.

You get one star reviews leaving you frustrated because customers are downloading your app on a device you don’t own. What if you could test on a thousand devices without spending all of your cash to get them?

With Xamarin Test Cloud you can!

Whether you are deploying an enterprise app or deploying a consumer facing app, Test Cloud allows you to test on 1000+ real iOS and Android devices to catch bugs before users do. You will avoid customers who are frustrated with low performance issues and avoid app killing one star reviews.

Let us show you what Xamarin Test Cloud has to offer, how to write and automate your tests, and potentially avoid those dreaded one star reviews.

So if you want to learn about Xamarin Test Cloud and how it can help you come join us! Pizza will be served from 5:30 – 6:00 before the presentation starts at 6:00.  Sign up here to join us for this time saving event.

And don’t forget, RedBit is a Xamarin Preimier Partner & a Xamarin Test Cloud Partner, so if you are looking to implement a cross platform solution for iOS or Android or need assistance in getting setup with Test Cloud contact us to get you going!

In the middle of a project where the team is building a customer app for iPad using Xamarin a requirement came up to automatically shut down the after a certain action was performed by the user.  Usually it’s recommended to not ‘kill’ your app on iOS and apps may fail certification if you do this.  Make sure to read the iOS documentation.

Now because we are doing an Enterprise Deploy and not an App Store Deploy, we were pretty safe.

I go in more detail in the post titled Exiting an iOS App using Xamarin on the Exiting an iOS App using Xamarin.

imagineCamp2Over the weekend I was at University of Ottawa presenting to the students in the Electrical Engineering and Computer Science program talking about building for Windows and Windows Phone and the best way to leverage and re-use code across the different platforms.  It’s always exciting to meeting and share with students my experience in software development and helping them along in their endeavours/careers.  You can read more about the event on the RedBit blog 

As a follow up here are bunch of resources and links to things I mentioned during the two days

If you attended (or if you didn’t, heard it was mid terms) feel free to connect with me here or via twitter to ask questions on developing for both Windows and Windows Phone or any other questions in general.

Next up will be Queens University register here and another one end of March in the Kitchener Waterloo Region (will post details on that soon).

Throughout my whole career as a developer I have always tried to participate in various events and speak at events to share the knowledge I have learned in developing software.  With the RedBit team expanding, I get introduced to new type of events and get excited to participate.


One of those events is the Global Game Jam and the specifically the Toronto Global Game Jam and the RedBit team will be participating. RedBit as a company has also decided to sponsor the Toronto Global Game Jam. At RedBit we are building some games for customers and used tried different software such Unity and MonoGame so we should be able to get something going in the 48hrs. I will be there to help encourage people to think about all platforms including Windows Phone (it outsells iPhone in 24 Countries), think about games that can go global and think about the female demographic as I think that is an area that is overlooked (45% of gamers are female according to The Entertainment Software Association)


Personally, I’ve played games my whole life and yes I did own Excite Bike. I continue to play games with my kids be it on XBox, Phones or desktops. I have also dabbled in creating games using XNA and going through the process with my son and created ‘hello world’ type games such as Tic Tac Toe and Memory Matching games.

I always get asked what tools should you use? We have used Unity3d and MonoGame with Xamarin, both are good and both allow you to go cross platform which is key in my opinion. At RedBit we are buildign using MonoGame and Xamarin as we are a Xamarin Partner and have all appropriate licenses. If you are building a game, you want to target the widest audience possible and using tools that allow you to go Mac, Windows, iOS, Windows Phone, Android is key. Marketing is also another key factor but that is another post entirely!

I’m excited to be participating in the Global Game Jam to see what comes out of it and feel privileged to be in a position where through my company I can help sponsor the event to help support the developer community.

Will you be there? Let me know as would be great to connect with you!

I have been involved in open data for a while now from a personal interest as a developer and a business interest via RedBit. I’ve participated in various hackathons, events, done presentation, open sourced some code and even help run an open data group called Open Halton where we try to work with cities and municipalities to open up their data.



Over the years I’ve seen many cities open up their data and even seen a Canadian National Open Data policy come into place via Data.gc.ca. It was also exciting seeing Open Data being tabled as part of the G8 summit where it is guided by the following principles


  • Open Data by Default
  • Quality and Quantity
  • Useable by All
  • Releasing Data for Improved Governance
  • Releasing Data for Innovation



Now the City (or Town rather) I live in (Oakville) is ready to open up the town data and is holding the first community meetup. I will be participating representing the developer community here in the region and how RedBit as a business has leveraged Open Data to generate revenue and most importantly create jobs.

If you are free Feb 5 2014 be sure to join as. You can register at EventBrite and we are holding two sessions to try and accommodate everyone.

Have you done anything with open data? Share what you have done in the comments below or via twitter @MarkArteaga



The first time I was awarded Microsoft Most Valuable Professional Award I was awarded for .NET Compact Framework which ran on Windows CE and Windows Mobile. Fast forward 10yrs later and was re-awarded for for the 10th time in a row for Windows Phone Development.

Over the past years, I’ve meet a lot a lot of people from all over the world who just love technology and sharing their knowledge with everyone around. Being from Canada, it is great to see so many new faces and people sharing their knowledge with the local community. There are over 4,000 MVPs around the world in 90 countries and it’s a privilege to be part of a group like this.


I guess now I’m considered a veteran to the MVP program, but here is to another year in the community and as a Windows Phone Development MVP. If you see me at a conference/event, feel free to say hi, always great to meet new people!


This article is also available on the RedBit Site

With the recent release of Social Cloud, I asked the RedBit team what are the top reasons for using Windows Azure Mobile Services and here is what we have.

Easy Third Party Authentication

Using the Identity feature of Azure Mobile Services allows developers to quick implement OAuth based authentication without having to worry about a lot of the plumbing code that is required when writing everything from scratch.

You can easily incorporate authentication with

  1. Microsoft Account
  2. Facebook
  3. Twitter
  4. Google

As a developer all you would have to do is

  1. Specify the keys in the portal
  2. Use the mobile SDK for iOS, Android, Windows 8, Windows Phone with application
  3. Authenticate via the SDK calling MobileServiceClient.LoginAsync()

Here is what it would look like from the dashboard to setup keysidentity


To learn more about this feature see Get Started With Authentication with Mobile Services

Data Storage

Most mobile apps written today need some form of data storage and usually the process is

  1. Figure out where to host it
  2. Figure out what type of database to use
  3. Write some REST APIs to access the data
  4. Make sure the APIs are secured

Using the data feature of Azure Mobile Services developers can quickly create data tables, secure the data tables for read/write operations and also write custom scripts to run when an insert, update, delete or read operation is performed on the data.

From the client side, using the SDK, you call the MobileServiceClient.GetTable<>() method and data will be retrieved.  If the data is secured via the portal settings, you will need to login using the client SDK before attempting to retrieve the data.

For more information see Get Started with Data in Mobile Services.

Client Libraries

Azure Mobile Services comes with clients libraries for the main mobile platforms available in the market today which are

  1. iOS
  2. Android
  3. Windows Phone 8
  4. Windows 8 (C# & JavaScript)
  5. Xamarin for iOS & Android

Leveraging this library and Azure Mobile Services on the back end, developers can focus on writing their app and not all the extra plumbing required for things such as authentication.

Custom APIs

The API feature is relatively new (as of Jun 24 2013) to Azure Mobile Services but allows developers to quick build APIs to the systems to be accessed by various client applications. You can quickly build out the APIs required by your app and just as quickly secure the APIs making sure only authenticated users have access to the APIs. Definitely something to use more often in the future!

Push Notifications

I’m a big fan of push notifications for mobile apps because it allows users to stay connected and engaged with their users. It’s also a great way to entice users to open your apps and this is especially useful if you are monetizing your apps with in app advertising.

Using Azure mobile Services, developers can quickly get this up and running on the various platforms such as iOS, Android, Windows Phone 8 and Windows 8 and it’s as easy as setting a few keys in your Azure Mobile Services Dashboard


Definitely something every developer should look at to keep their users engaged with their app.

For more information on how to get this running, see Get Started with Push Notifications in Mobile Services.

Overall, I think Windows Azure Mobile services really helps accelerate the development cycle and get your product to market faster. It allows you to focus on building out your product on not have to worry about server infrastructure or plumbing code required for things like authentication.  When you need to scale, it’s just a few clicks and you are ready to handle your extra load from your users.

So those are our top reasons for using Windows Azure Mobile Services. If you have used it, what are your top reasons? Ping me or the RedBit team on Twitter or leave a comment here.

This article is also available on the RedBit Site

Tracking and visualizing social media streams in real-time and across multiple social networks can be a challenge. Three months ago we set out to address this challenge, in partnership with our friends at IdeaNotion and Microsoft.

Today we’re pleased to release as Open Source the Social Cloud project.

social cloud logo-blue

Social Cloud allows users to monitor various social media channels such as Twitter, Instagram and FourSquare, aggregate and process that data (e.g. generate word clouds) and expose real-time streams to web & mobile clients.

The entire solution consists of the following:

  1. NodeJS “emitters” on Linux VMs running concurrently to monitor social media  streams
  2. NodeJS “server” exposing streaming data to front end visualization systems
  3. An admin web dashboard built in NodeJS & Bootstrap
  4. Native iPhone, Android and Windows Phone admin clients built using Xamarin
  5. Email, SMS, push notification & in-app alerts using SendGrid, Twillio & Pusher
  6. HTML5/Canvas visualization engine powered by IdeaCloud

Here is an architectural overview of the system that was built using Windows Azure


On the outside, seems like a pretty easy concept, but internally there are a lot of components to make this an efficient scalable system. Here is a list and description of all of the features used for the system.

Azure Virtual Machines

Windows Azure has the ability to run Virtual Machines or VMs in the cloud. The ability to spin up a VM in a few minutes is great from a development standpoint because we can spin up test boxes with minimal effort and minimal network infrastructure.

Social Cloud leverages this feature and we utilize Linux VMs to run our NodeJS processes. We went with a Linux VM because of WebSockets support and we needed a little more control than what Azure Websites provided. Also, the development team felt more comfortable with Linux VM instead of Windows and allowed us to easily start multiple NodeJS instances to monitor social media streams.


As you can see from the diagram, there are multiple NodeJS instances running each monitoring their own social network. In the case of Twitter, we were able to use their streaming API for realtime results while the others are using a polling techninque.  Once we receive the data, we store it in a mongoDB instance and pass a message off to Azure Service Bus for downstream processing.


Windows Azure Service Bus

Social Cloud uses the Windows Azure Service Bus to detach the process of gathering the various social messages from the processing of said messages to ensure that we can receive the messages as quickly as possible.  One of the different processes that subscribe to the Azure Service Bus topics are the Word Emitter that listens for text based messages and splits them into the words, processes them, then places new messages back onto the Bus.  Another subscription listener is the Socket.IO process that passes incoming messages from the bus to each of the listening Socket.IO clients.  This separation also provides the benefit of being able to withstand one component failing, as the messages are queued until the process is brought back online.


Windows Azure Websites

Social Cloud leverages Windows Azure Websites to run the administration dashboard which is written using NodeJS. This site also provided APIs to be accessed by iPhone, Android and Windows Phone apps. We leveraged the Git deploy feature available and the integration with BitBucket for automated deployments.



Windows Azure Mobile Services

Windows Azure Mobile services are one of the new features that is still currently in preview mode but we still did manage to use some of the features available for the Social Cloud solution.

Some of the features used are

  1. Data – this feature allows you to easily store data within your system from clients accessing the system. Specifically we used it to store device information when implementing push notifications. It also allows you to easily set permissions to read/write the data and also write custom scripts to run when an insert, update, delete or read operation is performed on the data
  2. APIs – APIs is a relatively new feature and essentially allows developers to implement some custom REST APIs required for the system. It also easily allows developers to add support for permissions to any operation performed.
  3. Push – this feature allows developers to create native push notifications to Windows 8, Windows Phone 8, Android and iOS clients. This is great as you can quickly get this infrastructure setup in minutes.
  4. Identity – authenticating users is usually required in mobile apps. Social Cloud required it as we only allowed authorized users to access the data. Using the Identity feature we were able to quickly add authentication to things such as Google, Facebook, Twitter and Microsoft Account.

Essentially, Azure Mobile Services allowed us to quickly implement features such as authentication on mobile clients, and let us build out the features of Social Cloud and not worry about plumbing required for things such as authentication.


Windows Azure Store

For Social Cloud, we leveraged various third party components to add features and functionality to the system. The store allowed us to quickly find and purchase the third party services relatively quickly to be integrated into the Social Cloud system. The following third party components were used in the system

  • MongoLab – store all the streaming data coming in
  • Twillio – send text notifications
  • SendGrid – send email notifications
  • Pusher – send notifications to clients connected on the web dashboard
  • New Relic – monitor the health of the system


Social Cloud is a pretty extensive system requiring many different custom components and third party components to produce the required functionality.  Using Windows Azure and the different features available such as Azure Mobile Services, Virtual Machines and Service Bus allowed us to build a robust system quickly and easily.

Over the next few days we’ll be posting some technical blog posts on the system but as of now all the source code is available on GitHub. Be sure to monitor this blog or follow me or the RedBit team on Twitter to get notified when the code is released.