1229
Google's shocking developer decree struggles to justify the urgent threat to F-Droid (www.neowin.net)
submitted 11 months ago by to c/technology@lemmy.world
298 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 11 months ago (6 children)

Beats me! I'm in the process of moving banking and payment off my phone in preparation for a Linux one. These things will very likely not work on non-proprietary devices.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 15 points 11 months ago (1 child)

    These things will very likely not work on non-proprietary devices.

    Depends on your bank. Most work on alternate OS (like GrapheneOS), and of course some don't. https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/

    If an app (especially bank) doesn't work, I forward them this and try to ELI5 that their current method is flawed and less secure: https://grapheneos.org/articles/attestation-compatibility-guide

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 11 months ago (2 children)

    I'm in the process of moving banking and payment off my phone

    Go on... How are you doing so?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 11 months ago (1 child)

    Going for plastic when paying instead of using a digital wallet, using the banks' websites for transactions instead of the app.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 11 months ago

    Oh, yeah, absolutely. Mobile apps should only ever be used for check-scanning or for features that the online banking simply doesn't allow (which would be messed up of the bank to do); same with mobile wallets.

  • permalink
  • fedilink
  • source
  • parent