EnAccess / EnAccess/micropowermanager-agent-app
[Feature Request]: Make MicroPowerManager Agent App Google PlayStore compliant
- Dominant language
- Kotlin
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Preflight Checklist
- [x] I have read the [Contributing Guidelines](https://github.com/EnAccess/micropowermanager-customer-registration-app/blob/main/CONTRIBUTING.md) for this project, if it exists.
- [x] I agree to follow the [Code of Conduct](https://github.com/EnAccess/micropowermanager-customer-registration-app/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://github.com/EnAccess/micropowermanager-customer-registration-app/issues) for a feature request that matches the one I want to file, without success.
### Problem Description
The mid term goal is to release the MicroPowerManager Customer Registration App to [Google Play Store](https://play.google.com/store/games?hl=en).
Before we can do that, we need to do some refactoring and dependency updates to our app.
This issue collect all related tasks.
### Proposed Solution
see above
### Alternatives Considered
see above
### Additional Information
_No response_
Contributor guide
Research direction
The issue names no files, tests, or entry points; begin by inventorying the dependency updates and refactoring needed for the app's Google Play Store release. Done means the agreed tasks are implemented and the MicroPowerManager Agent App meets Google Play Store compliance requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100