My first iPhone application on the appStore

by ManniAT 12. December 2009 18:34

On a lengthy bus trip after DevReach Lino Tadros from FALAFEL inspired me to do some work with MonoTouch.

Years ago I did a project for a customer which includes a tool that supports their drivers with “Section Control(s)”.

This system has different names and (AFAIK) exists in Australia, UK, Italy the Netherlands and in Austria.
In Germany the plan to install such a system in the nearer future.

In the UK it’s named SPECS and has over 180 Installations.

In our region (Upper Austria) a new installation will be activated at Dezember 18th.
Information in German

So I remembered the “old solution” (it’s still in use) and decided to build this thing for the iPhone.

The main reason for this application is security. Let me explain.

The systems work with very small tolerances.
In Austria for an example you have 3% or 3 km/h for limits of 100 km/h and above.

So this means to always watch your speed very carefully. And that means look at your speedometer.
BUT: with 50 km/h one look to the Speedo means 28 meters “blind flight”.

I’ve heard rumors that some of my customers drivers abuse the system in the following way:
There is traffic and a limit of 80 km/h on a section  3 Kilometers long.
Due to the traffic they can go only about 50 km/h for about 2 Kilometers.
After this Section Controls shows (of course) that his average speed is 30 km/h below the allowed, so … Devil

Anyhow – the reason for Section Control is safety. You don’t have to watch the speedometer that much; Section Control will give an acoustic warning if your exceed the allowed average speed.

Back to building the application.
MonoTouch enable me to use a lot of the Windows Mobile C# Code for the new project.

Messing around with “Key-chains, provisioning, contracts,…” and all that other funny Apple stuff it took me about a week to build a development environment that does all I need.
This means – Max and PC Share a G15 Keyboard and my my 24” Main Monitor (I usually work with 2 19” Monitors and one 24”)
I have Windows Keyboard-Mapping on the Mac, shared drives…
Last not least I built a little tool to use MonoTouch Solutions in Visual Studio.

Anyhow, the infrastructure was done and it doesn’t take to much time to build the application.

UI Graphics took a lot of time in designer software, but coding was very easy. That’s one of the screens and it’s navigation animation :

Main     MainFlip
About 300 Kilometer of test driving later I was ready to put the app to the app store.

I read that it takes about 14 days for review. I did all I can to fulfill the rules for an iPhone application and so I was optimistic that Section Control will pass the review.


And YES – I submitted my application on Wednesday December 3rd (at about 1 am).
On Monday December 7th it changed the state from “Waiting for review” to “In  review”
Finally on Thursday December 10th an email arrived: “Your application is Ready for Sale” Big Grin

And since I early signed the “Artwork contract” I’m now allowed to use:



YES – the Image has a working link!!

So thanks to MonoTouch which allowed me to use my existing .NET skills for iPhone development and thanks to the (at least in this case) very fast reviewers at Apple my first iPhone application is on the appStore!!

I just submitted an article about some parts of the solution at – it will be reviewed and if gets published I will link it here.

Comments (5) -

12/13/2009 9:57:14 AM #

Ronald Widha

That's a very cool story. Glad to know that non Objective C is making it to the app store. Would it be right to assume then the client doesn't even know that it's a mono touch app? do they need to install mono touch framework as a requirement before being able to run your app?

Ronald Widha U.A.E. |

12/13/2009 10:28:23 AM #


MonoTouch is bundled to your app (and has to be since apple doesn't include it somewhere or provide a way to share code between apps).
So the negative part - MonoTouch apps are (about) 5MB+ applications. The 5MB is the framework.
On the other hand - you write little code or a lot of code - the size changes only little.
And with the latest Version 1.4.x MonoTouch reduced the release size by about 30%

So to clearly answer your questions: there is a little bit more startup time with MonoTouch (have a good default.png Smile) and the app size is larger than with native apps.
You don't have to take care about MonoTouch versions or deployment - it's always integretated into your solution.

From the perspective of the appStore deployment it's the same as if you deploy an Objectice-C application.
From the perspective of the user - (if he cares) the app is a bit larger than native apps and it takes a bit longer to start.
On the other hande - startup also depends on what you are doing in your code when your app starts. I found native apps which take significantly longer to start then Section Control

ManniAT Austria |

6/30/2010 6:55:54 AM #

Event management iphone app

It appears that you have placed a lot of effort into your article. I don’t really have much to say in response, I only wanted to say that wonderful work.
Keep sharing such valuable information.

Event management iphone app United States |

7/1/2010 2:39:21 PM #


I suppose it also will depend on how seriously you guard the quality of content revealed in your blog.


9/30/2010 7:44:41 AM #

 Exporters of Fruits and Vegetables

Keep up the good work.Your article is really great and I truly enjoyed reading it.Waiting for some more great articles like this from you in the coming days.

Exporters of Fruits and Vegetables India |

Pingbacks and trackbacks (2)+

Powered by BlogEngine.NET