Addressing specific technical topics

Unconference Session 2, Fri 11:15-12:15, Kensington Room

Prompt: <please write down a prompt at the beginning of the session or before it begins to guide your discussion>

Structured Notes

What are the key takeaways from your discussion?

Any ideas/proposals for addressing these issues?

What are the open questions you still need to answer?

Miscellaneous Notes

Update forms from push notifications in collect

• Notify of updates to form schema

• Causes full re-download of form with new version

• Media files are updated

• File limits?  Push uri instead of file

• Free-form messaging (custom messages based on what forms are downloaded)

Should there be a setting? In Enketo, the new version is always pulled with no setting

• Maybe it’s more of a server-level setting (+1!)
• Consideration: there should probably be some dialogs/notification when editing a submission where a new form is available

• Would be great to have “release notes” explaining what changed; might be nice to always have that info available

There needs to be a bigger picture conversation about what updating forms means

Always opted in, for all forms (is the customer requirement) - what are the ramifications for collect in general?

• What’s missing from the specification to make it happen?

Goal: try not to maintain a fork, see if we can agree on some integration points and shape the conversation for the coming week

Could build it as a standalone module that can sit alongside collect (or a fork of collect), initiating behavior via intents.

Could build it as a feature branch that both ships to a customer’s custom fork, and also used as a PR to the main line.

SMS delivery in collect

Fully-offline collect

App white labeling