I think that its better to collaborate and join forces of Helikon and Fearless Wallet teams, and here is why: Both apps aim to be open source and bring common good services to the ecosystem. In the "If you have seen similar proposals before: why is yours different?" There is no coverage of Fearless Wallet products, and what unique Subvalt will bring comparing to them. Right now Validators can use Fearless Wallet to manage their staking, and in the future, we will support Push-Notifications for alerts which are mentioned in the proposals (via decentralized Ryabina service). In addition to that, the proposal covers the effort spent developing libraries for Android and iOS, but Fearless Wallet libraries already provide enough feature-set and I don't see a need in developing another 2 native mobile libraries for Substrate, instead I would encourage the contribution and/or collaboration. Fearless Wallet iOS & Android libraries links: https://github.com/soramitsu/fearless-utils-Android https://github.com/soramitsu/fearless-utils-iOS Taking into the account that Fearless Wallet is the open source app for Polkadot & Kusama, I would suggest for Helikon team to consider a joint proposal with Fearless Wallet team on implementing 1) missing Validator features (set keys, view analytics & reports for Validator in-app) 2) decentralized notification solution (currently we are doing PoC with them) 2.1) mobile-side implementation of notification management 3) Fearless Wallet version with these features for wearables

Hello @antonkhvorov!

Thank you very much for your review.

Re: Substrate libraries

To be honest, as I also stated in our convo on the Kusama Direction channel, I didn't know about the Fearless Substrate libraries at the time of writing the proposal, I'm sorry about that, and thank you for pointing me to them.

Proposed solution for Android was to contribute to or fork the Polkadot Java library, and develop a new pod for iOS.

I'm all for collaborating on and contributing to the Fearless libraries. One feedback would be to rename the library to a more generalized name such as Substrate Android/iOS (or Kotlin/Swift), or something similar, so it gives a better idea at first glance. Although the Android library readme makes the function clear, the naming as it is now could make one think that the library is a specific utility library for Fearless applications.

I've already started playing with the Android library, and will soon start with the iOS one too, and update the proposal after I get familiar with them and Polkadot Java too.

Re: Merging of the applications

Fearless Wallet and Subvalt belong to separate domains: application and infrastructure tooling, and it is why Fearless and other possible wallet/staking applications were not included in the "Similar Proposals" section. Subvalt and Fearless should remain separate products, and they should grow in strong collaboration of Helikon and Fearless Wallet teams in their separate domains.

Re: Collaboration

To commence the collaboration and as a demonstration of intention I have submitted a very modest PR for the Android utility library readme. I've also opened an issue for Fearless iOS, and currently working on the code base to find a fix, already in the rabbit hole on my way to CommonWallet.

What's Next?

I will experiment with the iOS and Android utility libraries, and also with Polkadot Java, get more familiar with the wallet code bases too, come up with an initial framework for our collaboration, update the proposal and post a notice here by Wednesday latest.

Thanks again and let this be the beginning of a fruitful collaboration:) Please share any ideas and comments you may have in the meanwhile.