Change Details

#### Background This is the task to add native support for GPay into the Android Wikipedia App in partnership with fr-tech. Adding Native payment method support was one of the proposed enhancements identified for improving donor experience in the apps. Fr-tech and the iOS team have already added support for ApplePay. Adding support for Google / Apple Pay was also a [[ https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Mobile_and_apps#Accepting_donations_from_mobile_apps | request in the 2022 Wishlist ]]. #### Requirements - Entry points for flow: 1) From the "Donate" option in settings 2) from an in-app banner - An option to pay via GPay should be presented when tapping Donate - The GooglePay option or any branding should not be visible if the user doesn't have GooglePay set-up or is restricted for compliance reasons. In this case, the user should be sent directly to donate.wikimedia.org - Tapping "Donate with GPay" should launch the Payment Authorization view controller/action sheet - Tapping "Other payment method" should launch the #### Technical notes - The donation flow should be presentable from any context. - For now, we don't need to keep track of successful donations or keep any local information about donation history. In the future, we may want to record a donation that has occurred to prevent additional asks from being shown, but for this version, no record of donation is required. - This feature must work well with Dynamic Type and Voice Over. #### How will we know we are successful? Indicators: - 4.0% average CTR across both apps per unique user, with a higher increase in CTR on Android in December - 30% higher donation completion rate for native payments as compared to web view Curiosities: - What percentage of users use native payment method as compared to users paying with Apple pay or Google pay on Web? #### Designs: TBA Can be based on ApplePay general flow (ApplePay Parent task with designs: T288285)

#### Background This is the task to add native support for GPay into the Android Wikipedia App in partnership with fr-tech. Adding Native payment method support was one of the proposed enhancements identified for improving donor experience in the apps. Fr-tech and the iOS team have already added support for ApplePay. Adding support for Google / Apple Pay was also a [[ https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Mobile_and_apps#Accepting_donations_from_mobile_apps | request in the 2022 Wishlist ]]. #### Requirements - Entry points for flow: 1) From the "Donate" option in settings 2) from an in-app banner - An option to pay via GPay should be presented when tapping Donate - The GooglePay option or any branding should not be visible if the user doesn't have GooglePay set-up or is restricted for compliance reasons. In this case, the user should be sent directly to donate.wikimedia.org - Tapping "Donate with GPay" should launch the Payment Authorization view controller/action sheet - Tapping "Other payment method" should launch the #### Technical notes - The donation flow should be presentable from any context. - For now, we don't need to keep track of successful donations or keep any local information about donation history. In the future, we may want to record a donation that has occurred to prevent additional asks from being shown, but for this version, no record of donation is required. - This feature must work well with Dynamic Type and Voice Over. #### How will we know we are successful? Indicators: - 4.0% average CTR across both apps per unique user, with a higher increase in CTR on Android in target campaign - 30% higher donation completion rate for native payments as compared to web view Curiosities: - What percentage of users use native payment method as compared to users paying with Apple pay or Google pay on Web? #### Designs: TBA Can be based on ApplePay general flow (ApplePay Parent task with designs: T288285)

#### Background This is the task to add native support for GPay into the Android Wikipedia App in partnership with fr-tech. Adding Native payment method support was one of the proposed enhancements identified for improving donor experience in the apps. Fr-tech and the iOS team have already added support for ApplePay. Adding support for Google / Apple Pay was also a [[ https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Mobile_and_apps#Accepting_donations_from_mobile_apps | request in the 2022 Wishlist ]]. #### Requirements - Entry points for flow: 1) From the "Donate" option in settings 2) from an in-app banner - An option to pay via GPay should be presented when tapping Donate - The GooglePay option or any branding should not be visible if the user doesn't have GooglePay set-up or is restricted for compliance reasons. In this case, the user should be sent directly to donate.wikimedia.org - Tapping "Donate with GPay" should launch the Payment Authorization view controller/action sheet - Tapping "Other payment method" should launch the #### Technical notes - The donation flow should be presentable from any context. - For now, we don't need to keep track of successful donations or keep any local information about donation history. In the future, we may want to record a donation that has occurred to prevent additional asks from being shown, but for this version, no record of donation is required. - This feature must work well with Dynamic Type and Voice Over. #### How will we know we are successful? Indicators: - 4.0% average CTR across both apps per unique user, with a higher increase in CTR on Android in Decembertarget campaign - 30% higher donation completion rate for native payments as compared to web view Curiosities: - What percentage of users use native payment method as compared to users paying with Apple pay or Google pay on Web? #### Designs: TBA Can be based on ApplePay general flow (ApplePay Parent task with designs: T288285)