Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • This is just parity with google wallet, right? AFAICT my library card in google wallet is just a generic card/pass type.
    by dschep
  • Good to see Apple catching up with Google finally.

    Google wallet has had the abillity to scan tickets and create custom passes for years.

    This article frames it like Apple are coming to save the day from lazy developers, but in reality its Apple who have been sleeping on this while other competing services have offered it for some time now.

    by alt227
  • Finally!

    An option to override automatic (un)archival of passes is also desperately needed. Some passes just don’t expire based on time, and too many pass creators are too incompetent to put the correct time in even if they do.

    Airlines in particular are prone to things like using local time in a field expecting UTC, which has made boarding passes auto-archive hours before leaving for the airport for me…

    by lxgr
  • 15 years ago, a friend of mine built an app to do this — "Pass Creator" — then Apple yanked the functionality.

    He paid me to create the icon for it, which was my first paid graphic design job: https://www.noio.nl/2012/10/pass-creator-app-icon/

    Thanks Paul.. good times!

    by noio
  • > A few places where we still help, even after iOS 27 ships:

    > Google Wallet. Create a Pass is iPhone-only. Roughly half of the wallet-using world is on Android, and our generator builds Google Wallet passes from the same form.

    What does this actually mean? Google Wallet has had a button to add your own passes for many years. How is the feature described here different?

    by Liquid_Fire
  • What a relief. My awful workaround was photos of all my membership barcodes labeled with a sharpie so that I can search "Gym" or "Library" or whatever to pull them up from OCR indexing.
    by randusername
  • While the author does mention the barriers to adoption, the premise— Apple was waiting for people to do something, but people weren’t doing it— subtly casts Apple as a passive entity in this scenario. The solution seems to be presented as Apple stepping in to make up for Developers’ inaction. If it’s been 14 years and there’s been very little adoption, this is clearly a UX problem. How many small venues or libraries have developers, let alone developers that do enough Apple-specific development work to have an Apple Developer account? In 14 years they couldn’t come up with an alternate solution? Maybe a less expensive administrative version of a developer account? It’s not users jobs to sell themselves on Apple’s products.
    by DrewADesign
  • The wallet app UI is the peak of Apple's 'single 20y/o in sf' design.

    Anyone that has multiple card from the same bank (because, say, you have a personal account and a shared account with your partner) has to do the "pick between the two identical looking top 20px of cards" dance every time they use Wallet to pay for something. It is mind-boggling that the current UI persists.

    by kilian

Explore Birbla archives