The project is about create an in-app wallet integration library for mobile apps that want their users to be able to receive and send payments without them having to store mnemonics offline or deal with private keys. This will reduce the barrier for people not knowing much about cryptocurrencies, encourage them to join blockchain communities and learn more about the use of Cardano ecosystem. Plus, this project will create a new open-source tool for building useful applications on Cardano. Therefore, it will be beneficial to developers on Catalyst community that they will be able to integrate it, contribute to it, or even clone it and change it to build another application. This contributes to accelerating the development of the network of Cardano-based platforms that expand and connect with each other.

I totally support the proposer's idea. Once the open library is ready with its live product, common people and developers will jump in and be excited to use and understand the product and code. It would open a way to any new development possibilities utilizing Cardano later.

An open-source project for secure storage of Mnemonics in mobile will add great value. It can be a good solution for low balance wallets with low entry barriers. There is likely to be an impact on security however for low value and quick wallets will definitely improve user experience.

A good suggestion for an open-source tool is to create a mobile in-app wallet for mobile Dapps. In comparison to the existing methods listed in the proposal, it will be extremely convenient. However, it would be fantastic if you could include certain risks for users of this mobile in-app wallet. I believe the security risk is the first consideration for people when deciding whether or not to use a mobile wallet. Because open source software is so widely used, one security flaw might lead to plenty of others, affecting a large number of people. Of course, identifying these risks will take a significant amount of time, and you are concerned that you will not be able to deliver your proposal on time. As a result, I would like to learn more about your strategy for completing this challenge and dealing with security issues.

The proposal presents good idea about a tool for users in Cardano to help people overcome problems when they make transaction in the system. The proposed solution is provided however, it is quite general as the reader could not understand what is the detailed plan, therefore, it could be better if there is more information about the in-app wallet integration library. Moreover, the solution is good but it does not really meet the challenge and the key metrics are not provided in this part, even it is mentioned a little in the proposal but overall it is too short and general. If the key metrics are listed, the reader would easily understand the content of the proposal. The risk of the project better goes straight to the main point as it will show the difficulties and the problems the proposal face.

The proposal is well structured and briefly written but still provides enough information on the impact of this project. As I can understand, this tool is quite simple and useful for people who are willing to use the dApp services but have a little trouble with the cryptocurrencies. Sometimes the process of developing mobile apps can be difficult and hard to be delivered successfully. Since developers can get access and change it to meet their application demand, they are motivated to easily build mobile dApps and take time to increase the quality of Cardano Opening Source Projects. After all, I believe that this proposal has given simple and effective solution to the challenge.

The aftermath of this proposal is colossal, considering most of the users going forward might have all the understandings of Cardano or blockchain in general. The plug-in and use feature would certainly come in handy. But I personally feel, there are many loopholes in the proposed idea. The convener makes no statement of how secure and dependable their solution can be, considering the private keys are stored on local storage. How does the team plan to gain the trust of users and how can the businesses leverage this to do secure transactions. The risks on the other hand are very blunt assuming there are far more challenges the team might face during the development of such an open-source secure application. Probably a tad bit more attention given in providing the readers regarding the aforementioned topics might shed more light on their approach.

The proposal includes a general plan but not detail enough to call it a roadmap. It would be better if they includes the actionable roadmap with specific KPIs for each stage of that roadmap. The key metrics are also need to improved.

The GitHub itself is not enough for project monitoring. The proposer and his team need to add some channels for public communication. Common people and fellow developers out there will know and possibly give some help for the development. Lastly, don't forget to put some projection numbers or tech stack achievements in the milestones for evaluation.

The proposal is for 10K USD to pay for a part time developerfor two months and a maintener of the repository. The proposal will output a react native library for storing mnemoics of the wallet in a secure manner. These are clear outputs with reasonable cost. THe project will be opensource. Therefore the proposal is highly auditable.

If you could provide the number of successfully completed tests required to be considered suitable for the project, that would be fantastic. I do not see any milestones or the road-map you mentioned, so it would be great if you could add them so I can check the project's auditability. To ensure that users do not have to worry about storing keys, you must ensure that the security risks I mentioned earlier are addressed. I believe the proposer should be more self-assured and share some more good metrics he required for this project's success.

The good point is that the number of successfully executed tests. But there is another advantage if the proposal mention how successful the project would be such as any numbers of traffic or the increasing of users and so on because the reader can imagine how is the proposal progress. It is a good idea to emphasize the tools or KPI of the proposal because it is easier to follow. Moreover, it is mentioned that there are some successful launched projects, it can be better to emphasize again as it can increase the feasible of the project.

The proposal has provided good key metrics in the proposal. There are 2 final deliverables but I think they should be provided with more details or a more straightforward way to measure/ evaluate them. Beside, a link to audit the process of the project should be provided in order to be clearly and easily tracked by voters and the community.

Although the project seems intriguing in a unique way, I feel the proposer could have given the community better verifiable metrics than the usual achieving milestone KPIs. The auditability section clearly needs some work and makes sure that the metrics are aligned to the challenge's requirements. The number of users using their tech, number of businesses incorporating their plug-in payment feature, number of monthly users and transactions…etc could have added more insights to the success of the project and made the audit process more straightforward. It's pretty unclear if the milestones set are deliverables or research that brings back the team with evidence for the further funding rounds. With this proposal being a completely new one, the community would expect a long-term view and future plans so that the team can build trust within the community and the voters.