IOS SDK preview

Our demo app built on the SDK with a few code lines.

As you may have noticed we where extremely happy and proud to have a prototype reading passports using NFC with iOS 13 beta 1 together with presenter validation and assurance a few hours after the beta becoming available.
For those of you not caught up in the tech lingo this can be explained as.
• By reading the document using NFC we get a digital signed representation of the information visually available on the front page. The upshot is that this is tamper proof even against nation state actors or spy safe if you will.
• Presenter assurance and validation is matching whoever presents the document to whom it was issued. Again in a way that will foil resourceful state actors with unlimited budget for deep fakes, image manipulation or Hollywood style makeup or mask producers.

Now this is not news since this is what we have been providing on Android for a while, the news is that this is now available on both of the major platforms. In reality this gives something close to 100% market penetration once iOS 13 has rolled out.

Show me the code please

First a few words on the guiding principles which are that we do the heavy lifting covering all aspects while you solve the business process requiring this to be performed.

let configuration = Configuration()
configuration.publicKey = "<your_public_key>"
configuration.privateKey = "<your_private_key>"
IDmee.identify(from: self,
               configuration: configuration){
    [weak self]result, identityDocument in
 
    // For example store to pass in prepareForSegue
    self?.result = result
    self?.identityDocument = identityDocument
                 
    switch result {
    case .ok, .failed, .closed:
        //Do something with the idMeeResult. In our case, pass it to the ResultViewController.
        self?.performSegue(withIdentifier: "toResults", sender: nil)
    case .backNavigation:
        //Do nothing. User clicked or swiped back.
        break
    }
}

That’s it for doing the basic process, there will be additional work to customize look and feel and inherent business logic based on the result. As you can imagine this is still not rocket science nor a Herculean task in terms of effort.

This is the same principles we have chosen for our Android version and our overall goal is “only 3 lines of code should be required to do this”. We are not quite there but as you may surmise by the example we are not to far beyond this goal.