Why you would use it

An edit screen looks like a form plus a request. By hand it is more: load the record when the screen opens, and keep it loaded while it is shown; fill the form once when the value arrives, and never again over what the user typed; turn a valid submit into the mutation, and remember which request is this screen's; show loading, saving, saved and failed from that request; notice when the record was deleted while it was open. A list needs its pages loaded, retained and extended, its columns labelled, and its rows offered to a picker.

foldkit-crud does that glue once. What makes it safe to use is what it leaves alone: the rows and the save state stay in Remote's store, the drafts stay in the form, and every status a piece reports is derived from them, so it cannot disagree with them.