1wallet Mobile Light Client #174
Labels
big project
Projects that will takes weeks to complete
frontend infra
Frontend infrastructure stuff (state management, etc.)
integration
Integration with other dApps or blockchain infrastructure
native app
Native app development
A question 1wallet users often ask is why there isn't a mobile app version of the wallet. The answer is simple: because no one built it yet. This may change soon, as several projects are undertaking this challenge. However, projects do face a litany of unique problems when they attempt to make the wallet work on mobile. To start with, they need to reconsider the role of Google Authenticator under mobile settings, decide where they want to store the wallet seed, and trade-off between security. They may use Kotlin or Swift to build their native apps, and find it troublesome leveraging the Javascript libraries provided by 1wallet. They may have to adjust their design to accommodate the fact that 1wallet may expire and its address changes every time the wallet contract is upgraded.
A wise programmer once said, an example is worth more than a thousand lines of code. And the old wisdom is very true in this scenario. With 1wallet Mobile Light Client, we want to achieve two goals:
The light client prioritize user experience and visual impression over everything else (without compromise on security):
The initial releases will focus on iOS exclusively. We may add Android support in the future. It will be written in React Native but the way it works should not be hard to replicate in compatible with iOS / Android's native languages.
The text was updated successfully, but these errors were encountered: