The current implementation uses GoogleWalletClient.savePass. It is therefore only possible to use this plugin with Google Wallet. If users chose to use another wallet application or even run on an Android Device without the Google Service Framework available, this plugin obviously won't work at all.
I would hence propose to additionally add the option to use the "traditional" Android way and share the pass (either as transit JSON or as PkPass) as an INTENT a compatible application can receive. For this use case, a PkPass file is likely more eligible than raw transit JSON.
Steps to reproduce :
- use a device without GSF
- open SNCF Connect
- open a ticket details page
- you won't see the
Add to wallet button since the GoogleWalletClient.getPayApiAvailabilityStatus will return unavailable
- be sad you can't import your TGV journey into your wallet since you don't use Google 😢
The current implementation uses
GoogleWalletClient.savePass. It is therefore only possible to use this plugin with Google Wallet. If users chose to use another wallet application or even run on an Android Device without the Google Service Framework available, this plugin obviously won't work at all.I would hence propose to additionally add the option to use the "traditional" Android way and share the pass (either as transit JSON or as PkPass) as an INTENT a compatible application can receive. For this use case, a PkPass file is likely more eligible than raw transit JSON.
Steps to reproduce :
Add to walletbutton since theGoogleWalletClient.getPayApiAvailabilityStatuswill return unavailable