You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2021. It is now read-only.
Our primary goal is to get to our MVP, and release a public beta on the Play Store.
By being on the Play Store, we can reach more users, get more feedback from the userbase, and collect more data about how the app is running.
2. What’s our MVP?
The List app proposes that we allow people to request photos, respond to requests, and obtain photos for use under a CC license.
Let’s focus on these three fundamental functions
Other than that, we’ll also need a flagging system in place to monitor content
I think we can cover these bases by building out the design in our invision demo: http://invis.io/MH3FLVEB7
3. Workflow
Let’s build faster; we can have Android and API/backend development happening concurrently
Now that we have a dev server at Playground, I can write placeholder endpoints that deliver examples of the responses Android needs while Matt is working on the database
Once Matt has the backend in good shape, he can hook it up to make fully functional endpoints; there will already be pre-formatted api responses for him to work with
Fewer blockers for Android and Matt doesn’t need to guess what response the app requires
4. Timeline
*Dates are internal release and public release respectively.
I like the idea. It would be great have a list with tasks (in addition to the issues list) to easily consult. Right now, I want to help, but I don't know exactly what can I do, and I waste some time looking for tasks to do.
I would like to translate the app to spanish, may I?
@AyoPrez a Spanish translation would be good, but not yet. We'd like to get to 7.0 before we consider translations. Features first, before we open ourselves to all of the translation efforts. Those are important to get right, and CC has its own community of affiliate organizations who'd like to help on that too.
1. Goal: Let’s get to beta!
Our primary goal is to get to our MVP, and release a public beta on the Play Store.
By being on the Play Store, we can reach more users, get more feedback from the userbase, and collect more data about how the app is running.
2. What’s our MVP?
I think we can cover these bases by building out the design in our invision demo: http://invis.io/MH3FLVEB7
3. Workflow
4. Timeline
*Dates are internal release and public release respectively.
4.0 – July 24, July 28
(I’ll be working on 5.0 features pre-4.0 release)
5.0 – August 28, September 1
6.0 – October 2, October 6
(e.g.: how many new responses you’ve received)
7.0 – November 6, November 10
The text was updated successfully, but these errors were encountered: