Judo participated at Xamarin Evolve this year in Orlando. Since Microsoft’s acquisition of Xamarin, this space has gotten hotter so we decided to be in the midst of the action and leverage the hard work we have done thus far on this platform. Below I interview Janice and Luke, who represented judo at Evolve, to capture their thoughts from the event.
What did you think of the Keynote?
Luke: I really enjoyed it, I think it just shows the strength of the platform that, even with Build a month earlier lifting the veil on a lot of .NET news and Xamarin’s big bombshell for the year, they had a lot to talk about. I liked Miguel’s presentation better but that’s just cause he got to hand out all the developer goodies.
Janice: I thought it was a really well structured delivered keynote, it set the tone for the rest of the conference, strengthened the case for cross-platform native development, and addressed the implications of the recent acquisition head on. The whole theme of end-to-end DevOps lifecycle management gave context and framed the new features announcement nicely. Also, the slides were beautiful, big kudos to their design team, I was mesmerised by the color palette!
After launching in the US last year, Android Pay™ is finally coming to the UK. It has enormous potential to make 2016 a very significant year for mobile payments. Android has a 51.9 %* market share in the UK which means millions of Android users will now be able to pay for things quickly and securely with just a single tap, whether in-store or in-app.
We have come a long way from the 4.1 iOS Objective-C SDK. Since the release, we have introduced our new collection of Swift SDKs, judoSwift, which simplified the communications with judo’s REST API, and paved the way for the feature rich judoKit. Our kit contains out-of-the-box functionalities like Address Verification System (AVS), 3D Secure, and other input verifications necessary for submitting card information for payments and other transactions. Together with our mobile-specific fraud prevention judoShield module, we provide the perfect basis that makes accepting transactions easier, simpler, and more secure.
In our pursuit to make payments in apps even more secure, and due to changes in PCI’s security standards, we are phasing out some older versions of our tech. This means you might need to upgrade to our latest SDKs by the 20th October 2016.
This guide will walk you through the steps needed to upgrade your app to the latest SDK.
In version 5.1 of our Android SDK, we wanted to introduce lots of new features, focus on improving the quality of the codebase, and make customizing the SDK to match your app’s brand easier. With this in mind, it made sense to completely rewrite the SDK from the ground up.
If you’re using an older version of the Android SDK (pre 5.1), you will need to complete an upgrade to this version by 20th October 2016 due to PCI Compliance changes that were introduced (PCI DSS 3.1).
To make the process of upgrading to version 5.1 as smooth as possible, let’s walk through the main steps required to get your app updated.
Security is at the heart of what we do here at judo, and to ensure that our platform and services are adhering to the latest security standards laid out by the PCI council (PCI DSS 3.1), we have made some updates to our API and SDKs.
These updates mean that we will be ending support for TLS 1.0 and below on 20th October 2016. After that date, any API requests or dashboard sessions will need to use either TLS 1.1 or TLS 1.2. (However, while not being immediately phased out, TLS 1.1’s days are numbered as well, so we would highly recommend an upgrade to TLS 1.2.)
This summer, I came across an opportunity to write my first SDK, so I leapt at it. As developers, there is something very appealing about writing software for use by other developers. It might be because of the sense of solidarity that you’ve made life easier for sisters/brothers in code, or the thrill of a backseat driver finally getting a chance at the wheel. That is until the realisation that the demographic you’re serving will also be the best equipped to critique your output, this is especially true when producing an open source repository.
So below are some lessons (some key, some trivial) that I learned while coding judo’s Xamarin SDK.