Executive Summary: This proposal will be for bug fixes and support of the Dash Wallet for Android for 6 months. This will be submitted after the next super block. Fee: 11 DASH per month for 6 months. 10 DASH/month for the actual work, 1 DASH/month to pay for Proposal Submission Fee. Feedback is appreciated. Longer Text Below (PDF is attached).: --------------------------- 1. Project Name: Dash Wallet for Android – Support and Maintenance Description and Goal Statement: In a narrative, describe project context and background. What is the business need that gave rise to this project? Describe the business drivers that created the problem, opportunity or business requirement. Examples: regulatory issues, outdated technology or technological advance, community request. The Dash Wallet for android is a popular mobile wallet for the DASH cryptocurrency. Like any software it requires maintenance (bug fixes) and support for the users when they report issues or ask questions via email, slack or other social media sites. Email Address / Website: hashengineringsolutions[email protected] http://www.hashengineeringsolutions.com/dashwallet-maintenence/ Vendor: Hash Engineering Solutions 4. Project Scope Statement Project Purpose / Business Justification Describe the business need this project addresses The DASH community has a need for mobile wallets and Dash Wallet for Android (https://play.google.com/store/apps/details?id=hashengineering.darkcoin.wallet) is one such wallet. Without well maintained mobile wallet apps, the DASH ecosystem will lack critical components in seeking adoption. With respect to this proposal, the Dash Wallet for Android has increased its usage by 50% since February based on Installs on active devices reported by Google Play (from 4000 to 6000). Hash Engineering Solutions created the Dash Wallet for Android in 2014 and has been maintaining it since. Objectives (in business terms) Describe the measurable outcomes of the project (e.g., reduce cost by xxxx or increase quality to yyyy). Describe what will be achieved and what will be delivered. What are the benefits that the project provides Dash? What value will this project deliver to Dash? What is the vision - what will business be like after the project is done? The vision of this project is to improve the user experience of the Dash Wallet for Android app which is one of the few mobile apps used by the Dash Community and one of the very few that supports InstantSend for sending and receiving Dash. This will be achieved through maintenance of the app (mainly bug fixes) and technical support to the users. This app and its continued availability on the Google Play Store will allow for greater acceptance of Dash and help increase the number of transactions on the network. Key Deliverables List the high-level “products” to be created (e.g., application to do aaaa, improved xxxx process, manual on yyyy) Maintenance of the Dash Wallet for Android Tech Support of the Dash Wallet for Android Manual for the Dash Wallet for Android · How to use the app · How to address problems/bugs until the next update fixes them Scope Describe the boundaries of the project. What is in scope and what is not in scope (e.g. This project addresses Dash to fiat exchange process in the Internet. Direct exchanges (hand to hand) are not included in scope)? Maintenance of the Dash Wallet includes bug fixes and importing any changes from Bitcoin Wallet for android (upstream). Changes from Bitcoin Wallet can include bug fixes, new features and optimizations. This proposal does not include adding any other new features to the Dash Wallet. Bug Fixes and Updates will be submitted to the following channels: GitHub: Source Code Dash Wallet for Android: https://github.com/HashEngineering/dash-wallet Dash Java Library: https://github.com/HashEngineering/dashj GitHub: Downloads https://github.com/HashEngineering/dash-wallet/releases Google Play (https://play.google.com/store/apps/details?id=hashengineering.darkcoin.wallet) FDroid (not currently setup) Support includes answering emails from users, responding to crash reports (via email also) and helping users who use other forms of communication (slack, reddit, Dash Forum, etc). Some feedback is useful and helps with fixing bugs. Additionally a manual will be written to aid with tech support. The manual will include work arounds for known issues. The avenues of providing support to users includes: Emails received at [email protected] Reviews left on Google Play (https://play.google.com/store/apps/details?id=hashengineering.darkcoin.wallet) Issue’s submitted on GitHub: Dash Wallet for Android: https://github.com/HashEngineering/dash-wallet/issues Dash Java Library: https://github.com/HashEngineering/dashj/issues Dash Subreddit (https://reddit.com/r/dashpay) Dash Forums (https://forum.dash.org) Project Milestones and Schedule Propose exact start and end dates for Project Phases (e.g., Analysis, Planning, Construction, Delivery). What date will the actual project work start? What is the anticipated date that the project will be delivered and project team disbanded? Are there any dates that will drive the project schedule? (Examples: regulatory, vacation…). Include known milestones and/or phases. This proposal is for a six month time period starting on 1 May 2017 and ending on 30 December 2017. Before 30 June 2017, updates will be taken from Bitcoin Wallet and integrated into Dash Wallet after thorough testing. Success Criteria How will we know when the project is done? How will the Dash team decide if the final deliverable is satisfactory? What measure will be used? The measurements used will be the number of bug reports and crashes from Google Play and via email, the number of installs as counted by Google Play and the app ratings from Google Play. These measurements will be compared to previous months. For the planned major update, the Google Play and GitHub will show the versions numbers with dates. Any bug fix updates can be accessed the same way. Major Known Risks (including significant Assumptions) Identify obstacles that may cause the project to fail. Risk - Risk Rating (Hi, Med, Lo) Hash Engineering Solutions is a single person. If there is illness or accident or other obligations related to personal issues or regular employment, support will be limited or delayed. Mitigation: documentation, good information about the wallet shared with the community, open source code - Medium Disconnection from the Core Team. Mitigation: maintenance of contact with core team to synchronize technology, branding... - Medium Constraints List any conditions that may limit the project team’s options with respect to resources, personnel, or schedule (e.g., predetermined budget or project end date, limit on number of staff that may be assigned to the project). The schedule of the planned upgrade to take changes Bitcoin Wallet may be impacted based on feedback from testers (if it’s limited). In the past some bugs took a long time to solve due to limited user feedback (not many crash reports sent or other descriptions from users was not sufficient to identify the issues). External Dependencies Will project success depend on coordination of efforts between the Dash core team, the project team and one or more other individuals or groups? Has everyone involved agreed to this interaction? This project does not depend on interaction with the Dash Core team unless there are significant changes in the Dash Network Protocol. The recent 12.1 upgrade was such an example because of its significant and breaking changes. That did require help from the Dash Core Team, but that type of event is not foreseen for this proposal. Members of the core team have been helpful in the past and are aware of this proposal. 5. Communication Strategy (specify how the project manager will communicate to the Sponsor (Dash community) and Project Team members, e.g., frequency of status reports, frequency of Project Team meetings, etc.) Reports will be prepared at the end of each month and will include: · The number of and type of bugs reported by Google Play and by Email as compared with the previous month. Any actions taken (such as bug fixes) will be noted. · The number of installs from Google Play for the month, compared to previous months. · The overall rating and any changes from the previous month 6. Reviews Planned (indicate what reviews this project plans. Monthly reviews are recommended.) End of Month reviews 7. Notes Fee = 10 Dash / month for the proposal items, 1 Dash / month to cover the proposal submission cost; 6 month contract.