Close/Repurpose Haveno frontend
Proposal closure / Repurposing of funds (3rd Sep, 2024)
- The proposed structure for Haveno is no longer feasible.
- No progress has been made in 2 years.
- A developer (kewbit) has stepped forward to work on the project.
- Due to these reasons, this proposal is deemed void and the remaining 453XMR will be repurposed.
215XMR will be used to fund a Haveno Multi-Platform Native App For Every OS that will meet all the functional requirements of a Haveno UI.
The remaining funds will be used for further Haveno front end related work in keeping with the original goals of this proposal (at the communities discretion)
Merge request reports
Activity
Haveno Multi-Platform Native App for Android, iOS, Windows, MacOS and Linux
Perhaps kewbit can elaborate. The UI for mobile will be given attention to detail as will the desktop experience. It's my understanding that further fine tuning for the desktop experience will be combined with design work in a follow up CCS should the community be satisfied with this proposal.
Hey rottenwheel!
Yes, it's for mobile, and also the other OS's mentioned in the description of the proposal. Since it's written in a natively compiled language, it's perfect for every OS, even if it wasn't for every OS, you'd still be able to compile the source for any OS anyway...
Therefore, it just makes sense to release an app for every OS!
Woodser is quite happy with the idea of expanding/improving the desktop design to fit more of his vision too from the Figma designs, which I've agreed to do as well, as per community approval.
You mentioned it's totally different, I'm slightly confused by this, could you elaborate just for my clarity please? If you look at the merge request you can see from the images on the page there is a UI, I do appreciate that none of them are desktop images though. I am happy to add some.
This all ties into having a unified frontend codebase, that is appropriate for each OS/Device.
I hope that addresses your concerns on this, if not please shoot back!
Edited by Kewbit
-
I concur, this makes sense for the initial release, and you may decide that there is no urgency for desktop redesign in which case the remaining funds can be preserved for future offerings. Though as you mentioned, if you’re concerned about funds exhausting entirely, there are options to open a new CSS, or, as mentioned in Matrix, I am happy to contribute maintenance and a some hours pro-bono as a noble cause.
@woodser The latest changes to the MR should reflect this:
- kewbit is working on the project, not 'taking it over'
- The remaining funds will be used for further Haveno front end related work in keeping with the original goals of this proposal (at the communities discretion)
I support repurposing 215 XMR towards Kewbit's work, which has shown results already and which I'm ready and excited to review. Kewbit and I have been in touch about Dart/Flutter implementation specifics (like re: bundling a tor daemon directly into the app) that have consistently reinforced my sentiment that this is already good work that merits funding now in order to justify open sourcing all of its code and to bring it desktop platforms as well as mobile.
Others may have overlooked that Kewbit has already released an early version of a haveno package which all Dart and Flutter packages will eventually be able to use to interact with the Haveno network. This sort of planning for the future and for re-usability is an encouraging note that funds spent here are going to bring more benefits than "just" a Haveno frontend
Monero needs more work surrounding swaps and exchanges and this will be a very helpful step for the community towards enabling seamless swap experiences for everyday users.
-
Oh yeah!
I’ll link that package here in case anyone is interested, though I started today, still fairly good progress. I have been slowly working through the release of the client publicly and no one has really noticed yet
I am also working on an I2P protocol client/engine for Dart, this one is slower and will take time, it’s no part of the remit of what I’ve scoped out in my CCS, but it’s something I’m doing I the side which I am enjoying enough that I shall implement it anyway, when I perfect it enough
Here is a link to both repositories I began working on seperately:
Work mentioned above, Native I2P Client Wrapper: https://pub.dev/packages/i2p
Native Haveno Client: https://pub.dev/packages/haveno
Thanks for raising a great point @sneurlax. The work being conducted is in fact being planned and implemented in such as a way that components can be reused in future projects too, there will probably a come a time where people want more than just XMR -> Fiat etc, at least with these libraries segmented it makes it easier for the developer to start integrating the work in to other larger projects such as swap sites of any kind. I’m excited to see how these packages will get adopted and used by the community. They are released under the same open source licence as Haveno too, AGPL v3. All permissive licensing FOSS.
It’s also great to see that sneurlax is as excited as I am, kudos! I’m sure we’ll be working together on this in the future if you ever get time.
Anyway, Goodnight!
mentioned in merge request !489 (merged)
mentioned in commit faa028e6
mentioned in merge request !503 (merged)
