Learn why building decentralized identity functionality into your existing solutions has never been simpler with the Indicio mobile SDK.
By Tim Spring
Indicio recently announced the new Indicio Proven mobile SDK which enables any organization to build digital wallet functionality right into their existing applications. This allows any existing mobile application to hold and share verifiable data and identity, which leads to faster, more secure information sharing and a better experience for the end user.
Recently I sat down with the developers behind the project, Patrick Kenyon (PK) and Kolby Kunz (KK), to learn more about their thought process and how this new piece of technology was created. You can watch the full interview here.
The following are a few excerpts from that conversation that have been edited for comprehension:
TS: Could you please break down just what is an SDK quickly for us?
PK: An SDK stands for software development kit, to be more specific, oftentimes if you have a feature that someone wants to implement in an app, an SDK will just be a library or an aid focused on implementing that specific feature in other applications.
TS: So for the proven mobile SDK it implements features of proven and digital wallet functionality specifically correct?
PK and KK: Yes.
TS: What problem were you given to solve that led to the creation of the SDK?
KK: We had resources that were limited just to react native, and we really wanted to be able to target native applications and go from taking native applications and targeting other Frameworks like react native or flutter that can consume native code and get it all in one place and one solid API that everyone can work with.
PK: The alternative would be to use multiple other libraries across multiple different apps, like if they’re trying to use a different platform. So say they’re developing for Android native and iOS native they’ have to get two separate applications or libraries that don’t exactly always line up and so with ours it does line up across all of the platforms we support.
TS: What was your approach and how did you get started with the actual build?
KK: That was a lot, and we sat down for a long time with team leads and had a lot of discussion multiple meetings of what are we going to do, and I think originally we set out and we’re like “hey we’re gonna have to develop this in Kotlin for Android and Swift for iOS and we’re going to have to try to make sure that they mirror each other” and we ended up finding a solution where we could develop just in one code base and cross compile to another and that really made it a lot simpler for us to be able to have like a unified API or application interface so that everything was the same whether you are on Android or iOS developing and using this SDK.
TS: Are there any features you’re particularly proud of?
PK: One of the features about the SDK that I’m happy about, that we’ve recently done, is the react native rapper, because we were able to take our SDK and prove that it works in both IOS and Android react native. We were also able to create the API so that the SDK stays the same between Android iOS and react native, and so if you’re building a different application or using a different platform you only have to learn the SDK once and it stays the same. It’s really sweet.
KK: I’m particularly proud of the proofs module, proofs as far as a decentralized identity concept is a very difficult concept to develop for, and there are a lot of pitfalls that can come with it, and I feel like our solution to get there is fairly robust. It’s a little verbose on the end consumption, but it gives the user a lot of power for being able to submit proofs and fulfill proof requests, so I was pretty proud of getting that one through the finish line.
To learn more about the new Proven Mobile SDK visit the webpage, or contact our team for specific questions or to get started today!
