Time-tracking MVP #31
Labels
discuss
Share your constructive thoughts on how to make progress with this issue
enhancement
New feature or enhancement of existing functionality
priority-1
Highest priority issue. This is costing us money every minute that passes.
T1d
Time Estimate 1 Day
technical
A technical issue that requires understanding of the code, infrastructure or dependencies
We need a way of keeping track of who is working on what for our project.
This will become a core feature of our product.
It's there on the MVP feature roadmap: https://github.com/dwyl/product-roadmap#mvp-basic-workflow
Essentially we are building a Todo List with a Stop Watch. ✅ +⏳
Hence the reason for us writing tutorials for these individual components ... 💭
Once you click/tap on
Start
it will insert atimer
record associated with theitem
see schema: https://github.com/dwyl/app-mvp-phoenix#create-schemas
plaintext
first.We have a sub-task to build the "capture" part in our
gitea-demo
(tutorial):LiveView
: Advanced Example > RT Colab gitea-demo#12PETAL
PETAL
Stack technology-stack#87 for this MVP becauseTailwind
looks a lot easier to build Mobile-first Apps with (thanTachyons
where it's still totally possible, but more difficult..._) and from listening to theThere is a checklist in that issue we need to try and complete as quickly as possible.1
LiveView
... 🙄 but that's "OK" for MVP!)Features
Auth
using https://auth.dwyl.com 🔒capture
task to be done asplaintext
. 📝Start
timer for the task ⏳Stop
timer ✅1We don't have to have complete tutorials for everything, but we need to capture the basics so that both we (our current core team) and other people can find our "learn-..." tutorial/notes useful. But our main objective is learning the tech/tools ourselves as quickly as possible so that we can build our MVP!
@SimonLab let me know if this is clear or if I can clarify anything ... 🙏
The text was updated successfully, but these errors were encountered: