MobileNativeFoundation / MobileNativeFoundation/Store
[Feature Request] Roadmap for Store 5
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.4k
- Forks
- 217
- Avg merge
- 18m
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
We're looking into Store 5, but don't have a good idea on when it will be out of alpha or what features / bugs are still left to be completed (or changes incoming).
Can you please provide some info on the game plan for this version of Store? How much are we expecting API's / implementations to change?
Describe the solution you'd like
Roadmap document of what's left to be done before Store 5 is out of alpha
Describe alternatives you've considered
We'll just wait till Fall of 2024 and check in to see the version that Store 5 is in.
Additional context
We'd like to contribute to the documentation around Store 5 to make it clearer and more understandable around its use case. Is this something the developers would be open to? (not sure how to add to the docsite either).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no documentation file or docsite entry point, so first locate the Store 5 documentation structure and review the current alpha status. The work is done when a maintainer-approved roadmap explains remaining features and bugs, expected API or implementation changes, and the path out of alpha.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100