Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Clarify Why our App MUST Be Offline-First #45

Open
nelsonic opened this issue Feb 18, 2023 · 0 comments
Open

Docs: Clarify Why our App MUST Be Offline-First #45

nelsonic opened this issue Feb 18, 2023 · 0 comments
Assignees
Labels
discuss Share your constructive thoughts on how to make progress with this issue documentation Improvements or additions to documentation enhancement New feature or enhancement of existing functionality question A question needs to be answered before progress can be made on this issue T2h Time Estimate 2 Hours technical A technical issue that requires understanding of the code, infrastructure or dependencies user-feedback Feedback from people using the App

Comments

@nelsonic
Copy link
Member

@rubensdemelo 🇧🇷 (Dart/Flutter Expert & Friend of @dwyl)
recently asked an excellent question in a Tech Stack thread:
dwyl/technology-stack#93 (comment)

Q: Is your "non-negotiables" offline first approach documented?
Would like to deep dive into this topic.
I also read about CRDT algorithm.

Note: edited for clarity. Original:
image

Given that this relates to our Product (App) 📱
and this is where we're trying to capture as much detail on the Product, 📝
I intend to [attempt to] answer his questions here. 🤞
The focus in product-roadmap is on the benefit to the person using the App not the tech. 🎯 (i.e. non-technical ...)

The CRDT algo question will probably need technical deep-dive as Rubens suggests. 🧑‍💻 #technical
Because there's a lot we need to clarify so that people aren't "confused" or "lost" about what we're doing. 🤷‍♂️
But the perspective of the person using the App comes first. 🥇

It's on my list: 📋

image

Will get to this in the next couple of days (currently on family weekend so have limited desk time ...) ⏳

@nelsonic nelsonic added enhancement New feature or enhancement of existing functionality question A question needs to be answered before progress can be made on this issue user-feedback Feedback from people using the App discuss Share your constructive thoughts on how to make progress with this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies documentation Improvements or additions to documentation T2h Time Estimate 2 Hours labels Feb 18, 2023
@nelsonic nelsonic self-assigned this Feb 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Share your constructive thoughts on how to make progress with this issue documentation Improvements or additions to documentation enhancement New feature or enhancement of existing functionality question A question needs to be answered before progress can be made on this issue T2h Time Estimate 2 Hours technical A technical issue that requires understanding of the code, infrastructure or dependencies user-feedback Feedback from people using the App
Projects
Status: No status
Development

No branches or pull requests

1 participant