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

Offline First vs. Online as a Feature #3

Open
janl opened this issue Nov 26, 2013 · 1 comment
Open

Offline First vs. Online as a Feature #3

janl opened this issue Nov 26, 2013 · 1 comment

Comments

@janl
Copy link
Contributor

janl commented Nov 26, 2013

[15:51:21] <@gr2m>   I also keep thinking about how this is different to native apps that have "online" as a feature. Or if it's the same. I swing back and forth :)
[15:51:47] <@gr2m>   I think to me, offline-first is for apps that _are_ connected, with all its benefits, without the suck
[15:52:26] <@gr2m>   compared to where "online" is a feature, that I explicitly use as a user, e.g. "send & receive" in an email client, or the "sync" button in certain apps
[15:53:20] <@jan>    yup, that’s two very good distrinctions to observe
[15:53:28] <@jan>    e.g. native apps tend to have online as a feature
[15:53:41] <@jan>    web apps have online as a default and only maybe offline as a feature
[15:54:19] <@jan>    but it is equally feasible to have online-first native apps, and that these are just two general design principles for apps in whichever environment
[15:54:31] <@jan>    it’s just that one environment (native) is more aligned with online as a feature
[15:55:24] <@gr2m>   +1
@kelvenus
Copy link

@janl Cool explanation. I came across this content from Couchdb site? Do you have links to more resources and documentation on setup and configuration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants