Change Details

**Primary target audiences** **Quant:** KR: 2% decrease in edit abandonment KR: Engagement with full page editing is comparable to Android KR: Increase in unique user edit rate Guardrail: Passes review from accessibility users **Qual**: No reports of reasonably fixable bugs with the native editor through the app store or our support email in a 30 day period post release **Measurement Plan** AB test if we see a higher rate of edits per person that engage with the new editor **Engineering notes** This task consists of 3 parts: [x] Appending the hashtag listed on [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b545162241_6_0 | page 5 ]] of the spec to the summary of all edit APIs. We will also be logging events to two different schemas: [x] Log init, abort, saveIntent, saveAttempt, saveSuccess, and saveFailure actions via the EditAttemptStep funnel in the appropriate locations (see [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b0ac103eb9_0_0 | spec ]]) of the new native editor flow. [] Create a new funnel that points to the app_interaction schema, and add events in the appropriate locations of the new editor flow. New actions are described in the [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b0ac103eb9_0_0 | spec ]]. There should be no need for a new Gerrit patch/MEP schema on the backend. EditAttemptStep and AppInteraction are existing schemas that we are hooking into.

**Primary target audiences** **Quant:** KR: 2% decrease in edit abandonment //(editattemptstep data) // KR: Engagement with full page editing is comparable to Android //(mediawiki_history data) // KR: Increase in unique user edit rate //(mediawiki_history data) // Guardrail: Passes review from accessibility users **Qual**: No reports of reasonably fixable bugs with the native editor through the app store or our support email in a 30 day period post release **Measurement Plan** AB test if we see a higher rate of edits per person that engage with the new editor **Engineering notes** This task consists of 3 parts: [x] Appending the hashtag listed on [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b545162241_6_0 | page 5 ]] of the spec to the summary of all edit APIs. We will also be logging events to two different schemas: [x] Log init, abort, saveIntent, saveAttempt, saveSuccess, and saveFailure actions via the EditAttemptStep funnel in the appropriate locations (see [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b0ac103eb9_0_0 | spec ]]) of the new native editor flow. [] Create a new funnel that points to the app_interaction schema, and add events in the appropriate locations of the new editor flow. New actions are described in the [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b0ac103eb9_0_0 | spec ]]. There should be no need for a new Gerrit patch/MEP schema on the backend. EditAttemptStep and AppInteraction are existing schemas that we are hooking into.

**Primary target audiences** **Quant:** KR: 2% decrease in edit abandonment //(editattemptstep data) // KR: Engagement with full page editing is comparable to Android //(mediawiki_history data) // KR: Increase in unique user edit rate //(mediawiki_history data) // Guardrail: Passes review from accessibility users **Qual**: No reports of reasonably fixable bugs with the native editor through the app store or our support email in a 30 day period post release **Measurement Plan** AB test if we see a higher rate of edits per person that engage with the new editor **Engineering notes** This task consists of 3 parts: [x] Appending the hashtag listed on [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b545162241_6_0 | page 5 ]] of the spec to the summary of all edit APIs. We will also be logging events to two different schemas: [x] Log init, abort, saveIntent, saveAttempt, saveSuccess, and saveFailure actions via the EditAttemptStep funnel in the appropriate locations (see [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b0ac103eb9_0_0 | spec ]]) of the new native editor flow. [] Create a new funnel that points to the app_interaction schema, and add events in the appropriate locations of the new editor flow. New actions are described in the [[ https://docs.google.com/presentation/d/10M0slX4Pf8KOQDXN9Mlp57WCv_1sltXD0F7ElF75F7o/edit#slide=id.g2b0ac103eb9_0_0 | spec ]]. There should be no need for a new Gerrit patch/MEP schema on the backend. EditAttemptStep and AppInteraction are existing schemas that we are hooking into.