Change Details

Target user for MEX is for wikidata editors who would like to edit on their mobile devices. Many mobile devices do not have a strong/reliable internet connection or large data packages. Our current implementation involves loading templates twice and its unclear what we're asking devices to load at what point Goal of this spike is to review how we're doing things and if we can improve the situation for low data users - If there are quick wins then they could be fixed as part of the spike - If there is a larger change needed, then this should be pulled into a new ticket Risk: Premature optimization. Lets focus on keeping prototyping fast. Are there two convos here? reduce load and double loading of templates. Maybe reduce load is better suited for M3- Editing Functionality Timebox: 16 hours

Target user for MEX is for wikidata editors who would like to edit on their mobile devices. Many mobile devices do not have a strong/reliable internet connection or large data packages. Our current implementation involves loading templates twice and its unclear what we're asking devices to load at what point Goal of this spike is to review how we're doing things and if we can improve the situation for low data users - If there are quick wins then they could be fixed as part of the spike - If there is a larger change needed, then this should be pulled into a new ticket Risk: Premature optimization. Lets focus on keeping prototyping fast. Are there two convos here? reduce load and double loading of templates. Maybe reduce load is better suited for M3- Editing Functionality Acceptance Criteria [ ] Spike results are reported in this ticket [ ] The double load situation is confirmed as necessary or unnecessary Timebox: 16 hours

Target user for MEX is for wikidata editors who would like to edit on their mobile devices. Many mobile devices do not have a strong/reliable internet connection or large data packages. Our current implementation involves loading templates twice and its unclear what we're asking devices to load at what point Goal of this spike is to review how we're doing things and if we can improve the situation for low data users - If there are quick wins then they could be fixed as part of the spike - If there is a larger change needed, then this should be pulled into a new ticket Risk: Premature optimization. Lets focus on keeping prototyping fast. Are there two convos here? reduce load and double loading of templates. Maybe reduce load is better suited for M3- Editing Functionality Acceptance Criteria [ ] Spike results are reported in this ticket [ ] The double load situation is confirmed as necessary or unnecessary Timebox: 16 hours