You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keeping the total number of API requests down accomplishes two things:
The total amount of data usage for the client is lower, which is important to people who have a limited data plan.
We keep under the maximum number of API requests for the "free" plan provided by our cloud storage platform, Parse.
With that in mind, I would like to brainstorm and figure out the best ways to reduce the number of requests.
One way, as mentioned in another issue, is to only send a request to update an item after all changes to that item have been made.
Another way, would be to have a mini state machine for when users are checkmarking an item, to give them a chance to uncheck if they accidentally checkmarked. That way, the update to set an object to checked would only happen when the user checks and item and doesn't uncheck it within 2 seconds (or maybe a shorter amount of time) or vice versa.
The text was updated successfully, but these errors were encountered:
Keeping the total number of API requests down accomplishes two things:
With that in mind, I would like to brainstorm and figure out the best ways to reduce the number of requests.
One way, as mentioned in another issue, is to only send a request to update an item after all changes to that item have been made.
Another way, would be to have a mini state machine for when users are checkmarking an item, to give them a chance to uncheck if they accidentally checkmarked. That way, the update to set an object to checked would only happen when the user checks and item and doesn't uncheck it within 2 seconds (or maybe a shorter amount of time) or vice versa.
The text was updated successfully, but these errors were encountered: