Offline decentralized password manager

Play Store Link (Archived)

Revamping a Decentralized Password Manager

At myki, I faced the significant task of revamping their Android codebase, which had not yet launched, with the goal of quickly reaching feature parity with the iOS version. In just two months, I achieved this, launching a functional first version. myki, akin to password managers like 1Password, Bitwarden, and LastPass, differentiates itself by using a P2P network for syncing, positioning the phone as the master device and browser extensions and secondary devices as the supplementary.

The development was in Java using the MVP pattern, with an emphasis on functional programming aspects I had absorbed from Kotlin, and integrating RxJava with Streams. Opting for Java was a strategic decision, considering my role in mentoring a junior developer familiar with Java, and at a time when Kotlin had not yet received Google’s endorsement.

A standout feature I developed was an innovative autofill functionality. Before Android introduced dedicated APIs for this, I creatively used the accessibility screen reader features to detect login prompts, displaying a messenger-style bubble for user convenience.

Security was a critical aspect, with end-to-end encryption to safeguard passwords and credit cards. The database was built using Realm, a document-based database, which provided an exciting challenge and a throwback to my early days working with MongoDB. The interesting thing about realm was the database schema was identical on Android & iOS, making our app data portable across platforms.

myki garnered positive attention, including a review by Android Police, highlighting its unique features and performance. However, in March 2022, myki’s journey took a new turn when it was acquired by Jumpcloud, leading to the shutdown of the myki product (Jumpcloud Acquires myki). This acquisition marked the end of an era for myki but also a testament to the value and innovation it brought to the password management space.