Proposal “dash-wallet-android-maintenance-support1“ (Completed)Back

Title:Dash Wallet for Android - Maintenance and Support #1
Owner:hashengineering
Monthly amount: 13 DASH (3609 USD)
Completed payments: 3 totaling in 39 DASH (0 month remaining)
Payment start/end: 2017-04-20 / 2017-07-18 (added on 2017-04-12)
Votes: 973 Yes / 12 No / 30 Abstain

Proposal description

This proposal will be to fund the Maintenance and Support for the Dash Wallet for Android for 3 months (May - July, 2017). 

Reports are here:  https://www.dash.org/forum/threads/dash-wallet-for-android-maintenance-and-support-1.14777/#post-128538

Fee: 13 DASH per month for 3 months (Total:  39 DASH).
10 DASH/month ($610) for the main developer (Total: 30 DASH - $1840)
1.33 DASH/month ($81) to fund a backup person for tech support (Total: 4 DASH: $244)
1.67 DASH/month ($102) to cover for Proposal Submission Fee (Total 5 DASH: $305)
** Conversion rate of $61/DASH as of 12 April 2017

More summary information to be added here by 16 April 2017, but the PDF below contains all the information.

This app is at:
  Google Play:  https://play.google.com/store/apps/details?id=hashengineering.darkcoin.wallet
  GitHub:  https://github.com/HashEngineering/dash-wallet/releases/

We have been maintaining and updating this app since 2014 (nearly 3 years).  InstantSend was added in 2016 (over 1 year ago).  During that time we did receive some donations, some of which came from masternodes for part of a year.  We are not part of the Dash Core team, but work with some of them.

In recent months the usage of the app has doubled from 4000 to 8000 active installs (Google Play stats) and the amount of bug reports and user issues has also increased significantly.  This proposal will fund maintenance, updates, bug fixes and user support and give the Dash Wallet for Android priority over other projects with which Hash Engineering Solutions is involved.

Full Text as PDF:
https://www.hashengineeringsolutions.com/wp-content/uploads/2017/04/Dash-Project-Proposal-Dash-Android-Wallet-Maintenance-May-June-2017.pdf

Preproposal Discussion:
https://www.dash.org/forum/threads/pre-proposal-dash-wallet-for-android-maintenance-and-support.14021/

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
0 points,14 days ago
We were behind in our release of the next big release, but it is finally being rolled out on Google Play. F-Droid will take longer.
Reply
1 point,2 months ago
Since we didn't get a second person yet to help with tech support, we will pay out up to 3.2 dash for those who send in screenshots in other languages and those that send in bug reports that result in bug fixes:

https://www.dash.org/forum/threads/dash-wallet-for-android-incentive-program-to-fix-bugs-and-get-screen-shots.15291/
Reply
1 point,4 months ago
Absolutely yes.
Reply
0 points,4 months ago
Amen
Reply
1 point,4 months ago
In the future do you have plans to implement instant or privatesend?
Reply
0 points,4 months ago
To be clear I already voted yes, just a question for future reference.
Reply
4 points,4 months ago
InstantSend is already supported not sure about privatesend.
Reply
0 points,4 months ago
Thank you Roman for giving the correct answer regarding InstantSend. It has been supported for one year. This app implements InstantSend nearly the same way as Dash Core, with notifications for both sending and receiving as far as whether or not the masternodes approved of the transaction.
Reply
2 points,4 months ago
Privatesend probably not due to the simple reason that the Android wallet does not mix
Reply
1 point,4 months ago
Thank you Dworf. It is correct that this android wallet does not have a coin mixing feature and therefore PrivateSend is not supported. I thought heavily about adding this feature, but my current understanding is that the Android wallet would need to keep an open connection with a specific masternode until mixing is complete. This cannot be guaranteed. The app itself is not always on the network (it will disconnect after a certain amount of idle time), but more critically, a mobile device's IP address changes based on which cell tower or WIFI network it is on - thus breaking the connection to the masternode. In the future it may be possible to resolve some of these issues if the user is required to stay on the same WIFI channel, for instance, until the mixing is complete or the mixing would be cancelled. Regardless of the reasons, this proposal does not cover adding a new feature such as PrivateSend.
Reply
0 points,4 months ago
Cool thanks for clarifying, I didn't realize instant send was already incorporated!
Reply
0 points,4 months ago
Its value for money, i vote yes
Reply
0 points,4 months ago
Voted yes. We have so much money, this is a no brainer.
Reply