Proposal “dashpay-ios-supplemental-1“ (Active)Back

Title:DashPay iOS Supplemental Development
Owner:the_desert_lynx
Monthly amount: 350 DASH (6979 USD)
Completed payments: no payments occurred yet (3 month remaining)
Payment start/end: 2025-02-06 / 2025-05-07 (added on 2025-02-11)
Final voting deadline: in passed
Votes: 452 Yes / 207 No / 24 Abstain
Will be funded: No. This proposal needs additional 82 Yes votes to become funded.
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many c2bc9e0bed3477dd49dcf7d8536a2d3f4cf96137ff2adb89f62305d285ecaffc funding yes

Please login or create a new DashCentral account for comfortable one button voting!

Proposal description

This proposal is to fund additional Dash Core Group development of the iOS DashPay wallet.

Development of the Android version of DashPay, Dash (and Dash Evolution)’s flagship product, has significantly outpaced development of the iOS version. The iOS team is currently under capacity and DCG does not have the means to hire additional help at current price levels.

I am requesting a 350 multi-month proposal to fund additional iOS development of DashPay by DCG, paid out to their address. I am also actively engaged in recruitment efforts to locate top developer talent who would be appropriate for filling this need.

This proposal is not an attempt to subvert or compete with any existing proposals. However, since last month the masternodes chose not to pay out about 500 Dash at all, I feel it appropriate to give the network the option to dedicate some of that funding to expedite iOS DashPay development instead.

All funds will be directly held by DCG, and will be dedicated to funding additional development work on the iOS version of DashPay. I will update the community on our progress recruiting developers. Thank you for your consideration.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
3 points,23 days ago
While iOS does have an issue, with my help things have gotten better and I believe we will release within a month. While this proposal might pass this month it doesn't have the commitment needed to hire someone else for iOS as if we were to hire someone, but then this proposal gets defunded, we would be in a bad situation. It was a valiant effort to try to fix a problem, but without strong support that we didn't see in the first month I think it's in the networks best effort to fund other proposals.
Reply
1 point,23 days ago
Does this mean you will not be seeking a replacement for the current iOS dev and trust that this iOS wallet developer can maintain the iOS wallet without your further help and not cause further development distance between the Android wallet and the iOS wallet or block development on Android wallet, due to iOS wallet getting so far behind with regards to developments ?
Reply
0 points,23 days ago
Letting go of the current dev and finding someone else would not have improved the situation. Because you need someone to train a new dev and about 4 months at the earliest for them to come up to speed on things. And then they might turn out to be bad. The only way things could have improved would have been to hire an additional resource. Absent that I think the way we fix things is with my help on common Rust frameworks proven to work that they can integrate.
Reply
4 points,27 days ago
To the YES voters, supporting this proposal will not fix the iOS issues, the problems they are facing are not a lack of funding, but rather organisational issues. It continues to be a NO from me. Please don't push out more valuable proposals, by funding this grift.
Reply
2 points,1 month ago
I am on android, could someone explain what exactly is wrong with the iOS Dashpay Wallet?
Reply
1 point,1 month ago
There is no iOS DashPay. The current wallet, Dash Wallet, is many months behind Android. Simply put there have been development challenges that haven't been able to be solved, and current developer resources aren't able to solve them.

We would basically recruit additional help to get DashPay released on iOS and feature parity with Android.
Reply
0 points,1 month ago
Gotcha thanks, I will vote yes, if it isn't being maintained that seems to be a huge problem for us
Reply
3 points,1 month ago
"I am requesting a 350 multi-month proposal to fund additional iOS development of DashPay by DCG, paid out to their address. I am also actively engaged in recruitment efforts to locate top developer talent who would be appropriate for filling this need."

Questions (that you are not going to answer)

1) Is the IOS code opensource?

2) If yes, then who decides what should be coded? Is it you who decide?

3) Do you have the skills to judge the developers?
Reply
2 points,1 month ago
4) If you are not a developer or you cannot judge the developers, why trust you in recruiting? You will fail, the same way DCG failed because they are also not IOS developers.
Reply
2 points,1 month ago
Ok...here is the code

https://github.com/dashpay/dashwallet-ios

What exactly do you want to be fixed in this code?

Instead of searching for salary slaves, why dont you give the specs and how much each spec worths, and wait for someone to code it?
Reply
4 points,1 month ago
Something has to be done about iOS development and this is likely the first good step. The status quo is unacceptable.
Reply
0 points,1 month ago
Whats wrong with it? You have to describe your problem, so that someone may start solving it.
Reply
-1 point,1 month ago
Any proof that the payment address of this proposal

https://chainz.cryptoid.info/dash/address.dws?7mUyau75ATy1c6LoZeG3D57jKBkR4iHJkE.htm

belong to the IOS developers?
Reply
5 points,1 month ago
The payout address is identical to the one posted by DCG's Quantum Explorer in this other proposal for this month. https://www.dashcentral.org/p/DCG-SUPPLEMENTAL-FEB25
Reply