Hardware and software for development

If you want to develop application for smartphones, you will need some hardware and software to start working.

Here is what I use to build native application for iOS, Android and Windows Phone.


> iMac 27″ : required to compile iOS application, enough powerful to have a VM with Windows working well
> iPod Touch 5 : try my apps on a real device at lower cost
> Galaxy Note I with a custom ROM which allows me to change the phone’s dpi and with Android 2.3 so I can still check that my apps works on old smartphone
> Nokia Lumia 930 : for Windows Phone application (and as my current phone)

Those devices allow me to test my app by myself on real devices. I feel like I develop faster by testing on a real device than the emulator because it builds faster.


> Inkscape : I love SVG as much as XAML. That’s the main reason why I create most of my assets with it.
> Mamp : Apache, Php, MySQL.
> Visual Studio Code : a light editor with Visual Studio shortcuts. I tryed it because Notepad++ isn’t available on OS X.
> Xamarin Studio : the main EDI I use.
> AppceleratorStudio for Titanium development.
> Vivaldi as my main web browser & mainly Safari to inspect my HTML elements.
> MySQL WorkBench : to modelize and manage my database.
> OneDrive : to keep some files available from everywhere.
> FileZilla : to upload my files.
> Virtual Box : to launch a Windows 10 instance so I can work on iOS and Windows Phone app with Visual Studio at the same time.

Other tools

> Balsamiq Mockup
> LinqPad
> Notepad ++

Starting a new project : PCL or Shared

Xamarin Team talk about pros and cons better than me. So follow the link below.


Shared project

> You only plan to target Android, iOS and Windows Phone
> You want to start coding as soon as possible
> You don’t plan to use Xamarin but you want to see how it works from a closer look
> You are familiar with #if directives

It works like if you were adding files as link. Every platform’s project will add the files from the shared project as a link. It means that when you add a file in the shared project, every reliant project will add this file.

PCL project

> You plan to use the project in other projects like an ASP.NET project, a WPF project, a Windows 10 app etc.
> You want to reduce dependencies
> You want to separate concerns


I’ve tried both way. I prefer the Portable approach. I’ve always been a huge fan of Portable Class Library and dependency injection. I felt I was coding the base of my application faster with the Shared project at the beginning. As an exemple, you can log what you want in the shared project because you have access to the Debug class. With PCL project, you don’t. So, you have to create an interface of a LogService and its implementation on each platform (e.g. AndroidLogService, iOsLogService, WinPhoneLogService). It’s the same thing with HTTP request : in the PCL project, you don’t have access to the HttpClient class. Thus, we have to make some extra work that isn’t necessary with the shared project.

If you don’t know PCL and dependency injection yet, you may start with the PCL approach as you will learn new interesting things.