Why you shouldn’t expect automatic upgrades to the latest version of Android

It must be tough working for an Android handset manufacturer if you’re the guy who manages their social media presence.

Every time you have something to say, no matter what that is, you have to deal with an Android power user who wants the latest version of Android on their 6 month old device.

I didn’t have to look far on the Samsung Ireland Facebook page for this:

So let me make this simple:

If you run and Android device, chances are you are not running the latest version. You can scream and scream at your operator or device manufacturer, but it is unlikely to happen

Here’s why:

Imagine you run the Operating System section of an Android handset manufacturer. You are tasked with building the operating system for your next device.

Now, in order to get this to market, you need a target that isn’t moving. So you grab the current stable version of Android from Google, and you get to work to make this work on your hardware. You do a ton of tests (and this is a LOT of testing); resulting in tweaks, patches and fixes, enhancements to take advantage of your cool chip, and so forth.

Then, you go to sell it; Your clients are mobile operators, who want very specific things added to their build. Simple stuff like reskinning, up to specific apps added as they need. So for each of your customers, you need to add some code, and so carry out per-customer testing.

During this time, Google have added enhancements to the operating system. Your choice now is to try to re-merge this, or release the stable, tested version you’re happy with. This is a no brainer choice. Even if you were to re-merge, the target could have moved again, so you simply aren’t going to do it.

Now imagine your device is out in the market. It has sold 1 million units, in multiple countries and on multiple operators. Google release “Neopolitan Truffle With Flake Topping” (or whatever they call the next Android O/S). Do you
a) Pull the new version, merge back in your changes, test, and then on a per-client basis merge their changes and test again, risking the possibility of releasing a bug which affects your 1 million clients ? or
b) Leave well enough alone, and keep the new version in your back pocket for the next device that you are already working on?

Exactly

Leave a comment

No. HTML5 is NOT the Answer

The cross platform versus native app question comes up again and again. Everyone knows where we stand on this; I truly believe that natively written apps, targeted for iOS, or Android, or Windows Phone 7, etc. produce more polished, better, more engaging apps.

I’ve never seen a brilliant app written in a cross platform way. And take a look at the apps that have grabbed recent buzz. Do you think Path or Flipboard ever considered a cross platform toolkit? I think not.

And, then I often get told that the answer is HTML5. One page rendered the same on all devices.

As Wayne was known to have said

“Shhhhyyyeaaah”

Look. Browsers differ, implementations differ, and as a result the output differs. Web designers all over the world still shudder when people mention internet explorer 6. The hacks to get web pages working across browsers was always an issue; and we’re being promised that we won’t have this in HTML5.

Or, as Wayne was known to have said

“And monkeys may fly out my butt”.

How do various browsers support html elements ? Well take a look here.
Wow. There’s a lot of red and green in there. Even a few sort ofs, “incompletes and almost.

How about CSS ? Well, lets look at that.
Oooh. We have yes, no, incomplete and buggy.

Wanna use some HTML5 advanced features. Sure. Go ahead. Just make sure you consult this first, mmmkay?

I know you want basic information, and you want wide reach, using HTML5 is a solution. However the promise of “it will work everywhere” may not be as true as you’d like it to be.

If you want a slick app, that shows your company, brand, service whatever in its best light, do yourself a favour and stay native.

11 Comments

Another outing for Velvet Rope

Those of you who attended the appys last Thursday may have spotted the app being used to sign people in.
Yes. Samsung gave “Velvet Rope” another outing.


Velvet Rope Appys Splash Screen


The appys were a great night. Many of our good buddies from XCake were winners; Congratulations to Axonista, Redwind, and App Sandwich; good guys all ’round.

Leave a comment

Velvet Rope

I love new interesting projects. This is a case in point. We already knew the guys in Samsung Ireland; After all they preloaded 2 of our Apps on the Galaxy S-II; We’ve been regular attendees at their developer events, and also at the odd product launch.

This time, they came to us with a challenge – They had a launch a couple of weeks down the road, and wanted something nice on the night to manage the guest list; Could we do it?

After our initial chat with Samsung, we had a quick brain storm. The brief was well…brief. Here’s what we knew:

  • The launch was going to be a high profile affair, with irish celebrities, models, etc. present (ok that ruled us out from attending!)
  • They location was Krystle Night Club. A well known, high end night club in Dublin.
  • They wanted to replace the usual on the door clipboard with a tablet device
  • They needed to pre-populate the guest list.

So, we brainstormed and came up with a concept we felt worked well; We called the night club management and spoke to them about how they typically made reservations, what happened when people cancelled, turned up with more people, etc. We visited the night club, and got photos of the various seated areas of the club, we took notes on their occupancy, etc. (Yes this was the boring part).

We wireframed and set to work, and the day prior to launch we had “Velvet Rope”

Velvet Rope allows the Night club owner to take reservations and choose where people will sit. It shows at all points occupancy of each section, and overall occupancy. It allows the host on the door to check people against the guest list; It all syncs to a central server, so multiple devices can run throughout the club (multiple entrances? no problem!)

Velvet Rope runs on Android Honeycomb. It is beautifully designed; It simplifies the job of guest list management. and it does it well.


Oh, and on the night, there were some great publicity shots.

1 Comment

We all have our rock stars

It was interesting to watch how twitter lit up around midnight. I’d reckon that about 90% of my twitter stream was made up of people’s thoughts on the fact that Steve Jobs has resigned.

It was overwhelmingly positive; There’s the odd mention that people should get some perspective, or leftfield swipes at the fanboys (fanbois?), but generally it was people wanting to thank Steve Jobs for the products that have made a change to their lives.

I understand that many see these tweets as pointless, or out of kilter with worse events going on around the world, but I understand it.

You see, different people have different heroes. Your heroes change throughout your lives; I know a girl who cried when Ayrton Senna was tragically killed, many weeped over Robbie being ejected from Take That; the tears of joy flowed when ‘King Kenny’ returned to Liverpool.

The point is this; we laud individuals because of talent. We build our heroes because of their talent.

– Driving Formula 1 Cars.
– Singing Pop Songs to 50,000 people at a time.
– Scoring goals, then being an even better leader off the pitch.
and even
– Making great products, that for some unknown reason, the owners don’t just like, they love.

So. When Steve Jobs announced his resignation, great software developers, brilliant designers, gadget lovers, techies..us…We felt the need to say thanks.

I’m not gonna apologise for that.

5 Comments

Welcome, Jason

Today I can announce that we’ve added a new member to the team. And with a new team member comes new capabilities.
Jason Connery joins tapadoo where he’s going to have a primary focus on Android App development.

Jason brings a wealth of server side API development experience to the company which will further strengthen our offerings; We all know that Apps are rarely standalone; A server side element is often required; Sometimes our clients have existing APIs, often we build them for them.

When not writing code, Jason is a keen gamer, reader and movie watcher.

Find him on twitter as @jasonconnery. I hope you will join me in wishing Jason all the best.

2 Comments

New App – Irish Sports Council Medications Checker

I always like announcing new releases; We don’t always get to showcase our work; Some of the work we do would be “proof of concept” apps which are used to sell ideas internally in a company, others are “white label” type deals where our client is selling on. But then there’s apps like this one. The Irish Sports Council Medications Checker.

Available on the App Store

What I like about this app is it that it’s the quintessential mobile app. The app makes a real-time request to find out if a drug is banned under the world anti-doping guidelines. If an athlete is about to take something to cure a headache, they need to know the answer on the spot, especially when they are find themselves in the pharmacy about to purchase some relief medicine. Now they whip out their iPhone, check, get their answer and record the fact that they checked right then and there. Job done.

I was at the official press conference last week. At this the Irish Sports Council published their annual Anti-Doping report, launched new initiatives around education and unveiled this app. Certainly the app got a lot of the focus and was featured on the Six-One news.

Press Launch of ISC Medications Checker iPhone App

Picutred are Dr. Úna May - Director of Anti-Doping, Michael Ring T.D., Minister of State at the Department of Transport, Tourism and Sport and John Treacy, CEO of the Irish Sports Council

Leave a comment

PSN Outage – Here’s what will have to be clarified

So PSN had an outage, and it is possible that all credit card details have been compromised. Sony have stated that credit card details, without CVV numbers may have been breached.

I’ve worked on a PCI compliant secure credit card store in the past, so I’ve some experience, and there’s a number of unanswered questions.

In a PCI compliant secure credit card store, you do not store credit card numbers in the clear – you must encrypt them. Encryption is easy (or rather, by standing on the shoulders of giants, it is) – Pretty much any platform offers you robust encryption libraries. The hard part is securing the key(s) used to encrypt/decrypt the data.

In the system I worked on, we used a dedicated hardware security module (HSM). This was a piece of hardware that was military grade – it never allowed the keys to leave the system, and had all sorts of physical tamper-proof capabilities. Basically it worked like this:

  1. The user supplies their credit card details
  2. The software asks the HSM to encrypt the data on its behalf
  3. The encrypted data gets stored
  4. When the system needs to use a credit card (i.e. take a payment), it supplies the encrypted data to the HSM and asks it to decrypt it
  5. The decrypted data is used to make the payment, and never stored

The security lies in the fact that the keys are secured, and cannot be obtained. If the database is compromised, the data is useless without a key; assuming you’ve used a large enough key, you’ll need a supercomputer to find it by brute force.

Sony have stated that all accounts have been compromised. This suggests a database dump as opposed to some ongoing “trace” to retrieve credit cards in the clear as they are being used. So here’s the questions I have

  1. Was a database dump stolen?
  2. Were the credit cards in the stolen data encrypted or in the clear?
  3. If they were in the clear, why?
  4. If they weren’t in the clear, has the key been compromised? If so, how?
  5. The same questions apply to users’ passwords

Of course, here’s another possibility:
The credit card data was encrypted and the key wasn’t compromised; Sony did everything right, but are using full disclosure to tell the worst case scenario. After all, a criminal with the resources to breach a major corporation may well have a supercomputer at their disposal.

Answering the above questions could put a lot of minds at rest.

Leave a comment

The “iPad killer” is on the way

No it isn’t.

If you’re a journalist and you write a prophetic article on the iPad killer you are either looking for attention from trolls, or are dumb.

I wrote about the “iPhone Killer” last year. Nothing has changed, and all the arguments remain the same.

Move along now, nothing to see.

Related: I’d love to have a product that everyone writes is about to be trumped by a new “killer”. Its a sure sign you’re doing it right.

1 Comment

Is this ipa signed for your device?

Its a common issue for iPhone app developers. You sign the build and put it on the web server. You download and it work on your own devices. You send the link to the client and the respond that it doesn’t work for them.

There’s a number of places where you could have made a mistake. You developer cert could have been incorrect.
You may have added their UDID to the portal, but forgot to add it to the provisioning certificate.
You may have added it, but not used the correct profile when making the build.
You may have done all this right, but not put the correct binary on the webserver

..and so on. We’ve all been there.

So, how can you tell if an ipa is actually signed for a client’s UDID. Well you could download/extract/find the provisioning file, etc.

Or you could use a handy command line script we’ve thrown together and put on github which does all this for you.

Hope you find it useful
https://github.com/dermdaly/listdevs

1 Comment