Skip to content
We have three refresh models for pulling sync table data: manual, daily, and hourly. What are our refresh models for pushing data?What are our rules for sending data under an automatic push model?
The ideal user experience is to send data once the user has finished writing. Thus, our rules should aim to guess when the user has finished writing.Retain flexibility to write the rules: we may need to balance infra load and adjust our heuristics over time. Thus, don’t set an SLA for sending updates until we refine
Time since last editcurrent cursor positionis doc active (e.g. is window active, mouseover, etc)
4/21: How frequently do we push updates to the 3rd party service?
Last edited 838 days ago by Punit Shah.
Stage: Proposal, please add feedback!
Context
Slack message
codaproject.slack.com
Key questions
1. What push models do we offer?
Push models
Option
Description
Why
Proposal
Proposed default push frequency
Build for v1!
Do it, but later
Never do this!
Manual
Click some “push” button and only then are updates sent.
The most “safe” option, and thus needed for any scenario where the user may want the flexibility to write the full set of changes and then send.
Build for v1
Time-based: Hourly, independent of pull
Send every hour, disconnected from the pull schedule
Never build this
Time-based: Daily, independent of pull
Send every day, disconnected from the pull schedule
Never build this
Time-based: Tie to pull schedule
At the same hourly/daily schedule as pulling, push updates
Seems useful, but most scenarios probably will use manual or automatic. We can build this, but can we defer?
Ok to build this, but post-v1
Automatic
Send some moments after the user finishes making edits, based on our own rules (defined below)
This is the most magical and ensures that writes get to the 3rd party service quickly but without much user thought.
Build for v1
Button / action formula
Similar to what we did for table pulls, to allow canvas buttons to push updates
Ok to build this, but post-v1
There are no rows in this table
2. What are our rules for sending data under an automatic push model?
Principles
Potential parameters to use
Add a topic
Add a topic
Dory: Topics for discussion
Discussed
Search
Idea
Author
Upvote
Notes
Discussed
Are there any blockers or dependencies to this launch?
Open
When are we expecting to launch?
Open
Have we considered user testing?
Open
There are no rows in this table
Add your sentiment
Add your sentiment
Pulse: Team sentiments
Author
Search
Sentiment
Reflection
Author
I feel great about the proposal—it’ll solve a problem we’ve been circumventing for a long time.
I worry about how this will affect the mobile experience.
Cautiously optimistic!
There are no rows in this table
3.67
Average
3
Count
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.