Linknode are an app development company. We have have a portfolio of apps available across different platforms and their stores. We focus on cross platform sensor driven applications that fit with in our Mobile Geography domain. This post is going to be a tour around our app portfolio and what we learnt along the way.
How it started: EmergencySMS
Linknode’s early apps were all for the Windows Phone market. It all started with the launch of Emergency SMS in June 2011 (the company was 2 months old at the time). This application takes the devices location, looks up the address and creates an SMS message that can be sent to the UK’s National Emergency SMS.
EmergencySMS is still available in the Windows Phone marketplace, and is still used by customers: it gets 10-20 downloads a day. I don’t consider it a masterpiece of design or implementation but it is a good place to start.
- Start small, your apps may last longer than you think.
MegaTile – free version and premium features
Another consumer app (and most successful in terms of revenue generated) is a called MegaTile and allows the user to customise their home screen on Windows Phone 7 and 7.5. The user can choose an image to make a MegaTile from and set an action (launch phone dialler send SMS, open web page etc.) for each tile.
- Have a free version, it make users download it and gets them to convert to the full version. 7% of our users purchased after running a trial.
- Test the upgrade process of your app on each release. We didn’t and caused ourselves a lot of negative comments from users who were unable to upgrade between v1.2 and v1.3.
Album Flow – Use a Design Pattern
We had an idea to bring the iOS style coverflow to Window Phone, this resulted in the Album Flow application. The initial version of this app was ready in 3 days. We are just polishing our 9th release and have over 100,000 users. Album Flow was featured by Appvertise (Nokia and Microsoft) and won a CreativeBloq App Generator Top Ten App.
- Use a design pattern to make your code consistent and understandable. We use the MVVM pattern and the MVVMLite library to support it.
- Respond to user demand and comments to get better reviews and more satisfied users.
Starting out in Augmented Reality
Where On Earth, and its cut down version – Heads Up Compass, are two apps that started to define the GIality concept and are the first examples of the use of GIality on a mobile.
Heads Up Compass takes the data from the devices motion sensor, uses it to work out which direction you are looking and superimposes that on the camera feed. Calibrating the compass and getting accuracy from the device sensors is hard. Use the Combined Motion API on Windows Phone or equivalent on Android or iOS for better results than just a single sensor.
Where On Earth goes a step further and looks up features around you to help identify features (hill tops and towns currently) that you can see in the camera view. Where On Earth was customised for a team entering the Oxfam Trail Trekker to provide them with a heads up display of check point locations and distances.
- Review your maths text book: Quaternions are good when working in Augmented Reality situations, but complicated to get your head round.
- Mobile apps should work when out of mobile signal. Design to manage offline access and syncing data. These a whole other blog post in this topic.
Windows Phone Development Summary
All of the apps covered above are only for Windows Phone. I love the process of developing for Windows Phone.
- The tools are excellent – I can use Visual Studio (which I have plenty of experience with and is set up exactly the way I want it).
- I can switch to Expression Blend if I want to do some more complicated user interaction.
- I can use C# a popular language that many developers who have worked in enterprise understand.
- Having come from a web background, I would much rather do layouts in XAML than in HTML / CSS.
My biggest complaints so far have been to do with the store and submission process (not being able to cancel an app being certified) and understanding some of the SDK design decisions taken to do with the back stack and Navigation.
Evolving Beyond Windows Phone
In mid 2012 we decided that Windows Phone was not a big enough market for some of our mobile geography plans (Although it may be getting there according to the latest stats from Kantar). Specifically we wanted to expand into using running our GIality solutions on a tablet. Whilst Windows 8 was coming (it launched October 2012), we wanted to start running GIality apps on tablets right away. We chose Android as our first tablet platform: specifically the Nexus 7 and when it was released the Nexus 10 .
VentusAR: Support for Android
Our first cross platform app was VentusAR. This is a Business to Business application (so it’s not available in the Play Store) to allow you to visualise what a wind farm would look like if it was built as planned. There are many different parts to VentusAR that all need to work together and need to work across multiple platforms. The main application logic needs to be complied by the Windows Phone and Mono for Android compilers (we’ve since added Mono-touch for iOS and Windows RT compilers too).
Coming from a Windows Phone background, Android development (even using Mono for Android and Xamarin tools) feels a bit of a disjointed mess. I guess it comes of saying anyone can customize the OS to run on any hardware (the Android approach) rather the OS will only run on our hardware (Apple) or the OS will only run on hardware that meets strict guidelines (Microsoft’s approach).
- Think about making the app cross platform-able early on. Its easier to start that way than to try to change an existing app to be cross platform.
- The android emulator is too slow to use for real development, buy a proper device to develop on – it’s much quicker.
- Android Resource qualifiers (screen resolution, pixel density language etc. make designing and testing Android UI’s very hard. The Xamarin Designer helps a lot.
- Run an automated build server as changes in the android app can have unintented affects in the other builds.
3DTry.it: Available for Windows Phone, Android and iPad
Our first public cross platform GIality app to launch is 3DTry.it (available for Android, iPad and Windows Phone). This is an app that allows the user to view published 3D models on their tablets on top of the the camera view. The models rotate as though they are in the real world. Download it from the app store if you want to see it in action.
- The motion sensor frame of reference is different on different devices (the nexus 10 is 90°different from the Nexus 7).
- Xamarin tools allows iOS apps to be developed on a Windows PC which speeds up development for windows users.
Having tried developing apps for all three platforms, I enjoy developing for Windows Phone the most (maybe that’s because it was the first one I started developing for). Android is frustrating due to the number of different devices, screen resolutions and version available. iOS development in c# is made easy using Xamarin tools, which have done the job for us so far.