Gallery
Some of my favorite rituals to organize a product team: ACME Project Hub
Share
Explore
Writeups

icon picker
4/21: How frequently do we push updates to the 3rd party service?

Last edited 532 days ago by Punit Shah
info

Stage: Proposal, please add feedback!


Context

Alicia Salvino
#story-packs-2-way Tue, Apr 18, 2023
not yet - pending exactly what those options are (cc ) i assume we’d start with another dropdown similar to the refresh / pull rate selection.
my suspicion is that we’ll need to reorganize some of the panel with these increasing number of settings but given our need for more feedback on staging and some similar work on i don’t think it’s worth investing a ton of time here just yet, probably better to start with the bare min UI to make it work
See more
codaproject.slack.com

Key questions

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?

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.
Time-based: Hourly, independent of pull
Send every hour, disconnected from the pull schedule
Time-based: Daily, independent of pull
Send every day, disconnected from the pull schedule
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?
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.
Button / action formula
Similar to what we did for table pulls, to allow canvas buttons to push updates
There are no rows in this table

2. What are our rules for sending data under an automatic push model?

Principles

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

Potential parameters to use

Time since last edit
current cursor position
is doc active (e.g. is window active, mouseover, etc)

Add a topic

Dory: Topics for discussion
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

Pulse: Team sentiments
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

Share
 
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.