Zippie Product Update — July 2018
July was a holiday for most of our R&D personnel, but nonetheless, we still had a very busy month. For a start, we released our Alpha 2 version. The Alpha 2 release was specifically for our Alpha testers, and so far the feedback has been pretty good. Zippie’s 20 second onboarding is now closer to 10 seconds. The UI style has been updated and a personal multisig wallet was introduced, which makes it possible to send payment links to anyone. This even includes people who don’t have a cryptowallet. What’s more, Pay My Gas server takes care of GAS fees on behalf of the user.
Preparing for the Alpha 3 release
Since the Alpha 2 release, we’re trying to maintain faster release cycles, and we’re aiming to make the next one in the next week or so. The Alpha 3 release focuses mostly on fixes and small improvements.
- Fix for iOS 11.4 onboarding.
- Copy-to-clipboard functionality for sharing payment links also on iOS and desktop environments.
- The possibility to add a message for payment links.
- Show transaction message when claiming the payment.
- Transaction detail view to see more information about a transaction such as full message and timestamp.
What about the Zippie card functionality?
We decided to postpone Zippie card features, because bug fixing has taken more time than anticipated and because we’ve had less resources over the summer holiday season.
The Zippie card features will be in the Beta 1 release and include Security tab changes. The Security tab will be a hub for devices and cards. The idea is to show all the devices that have been enrolled onto Zippie as well as your Zippie cards. The user can rename, add and remove the devices or cards. Therefore, if, for example, a device with a Zippie account is lost, it can easily be revoked.
But one of the most important features will be recovery using Zippie card. This is one of our main aims for our Beta 1 release.
Security Audit
The Security audit is proceeding as planned. Our Security audit partner has filed a few related bugs to be fixed, but happily there’s not been any major security flaws so far. We’re now working to fix these bugs to ensure your tokens will be as safe as possible.
Moving to Ethereum main net
Before we move to the Ethereum main net, we need to fix issues found from the security audit and make sure that the Zippie ID recovery works flawlessly using the card and other devices. When we’ve reached this level, Zippie will move to the main net and step to the next Beta level.
Distributed Application Development
We have one dedicated developer documenting how dapp developers can migrate to Zippie, for example, from Metamask. All these documents will be available in our GitHub repositories, which we are planning to open after the Security audit. Thanks to our CTO Carsten Munk’s vision, the feedback has been that it’s really easy to start using the Zippie vault and the wallet. In short, it works just like magic!
That’s all for now. But remember, if you’ve got any questions, be sure to get in touch via our Telegram channel. You can also follow our progress and join our community on Twitter, Reddit and YouTube.
Thanks for reading!
