Attendize
Attendize copied to clipboard
Attendize
Passbook support
I noticed that you support QRCodes, but it is not mentioned to support Passbook by Apple, do you plan to add it?
I don't see any reason why Passbook shouldn't be added as an option. However, I've no experience working with Passbook so I'm not sure how big of a job it is to implement it.
If anyone has experience in this area feel free to chime in!
We could use this https://github.com/eymengunay/php-passbook
To integrate with it it does require an apple developer account. which is about $99 a year (in aus)
To integrate with it it does require an apple developer account. which is about $99 a year (in aus)
only if you plan to update them remotely from your server to the user phone. Which is a nice to have but definitely not mandatory. Generating passbook is super easy it's a formatted file, with a format to follow. Could be done with a view ...
To integrate with it it does require an apple developer account. which is about $99 a year (in aus)
only if you plan to update them remotely from your server to the user phone. Which is a nice to have but definitely not mandatory. Generating passbook is super easy it's a formatted file, with a format to follow. Could be done with a view ...
@clawfire Am wondering if you ever created the view required for passbook. It sounds like you have experience with creating for Passbook?
hi @justynpride ,
First, I want to clear some things: recent changes in iOS (mid-2020) require now a certificate to sign the passbook to let them be displayed in the Wallet app on iOS. But there's a bunch of web services that let you generate passbooks using their certificate (with a free plan, paid plan if you go over xxx pass/months).
So, if we want to have a passbook with Attendize, I would recommend having a modular approach like with the payment, implement the first gateway which should be "buy an apple account and use your own certificate" and people can contribute connecting external services if they want?
Optionally that could be a service sold by Attendize. To use their certificate to sign the passbook (I already made lambda functions doing this for my https://github.com/clawfire/covid19-passbook-generator project, I can help you with it).
@clawfire Thanks for the really helpful reply. It's good to hear implications of recent changes, and possible solutions for Attendize. I really like the thought of it being modular so you can add in details for various 'gateways'. It feels like something that would really benefit Attendize.
In terms of my own prioritizing of development, this feature would be way down my list. For instance I'd love to see additional questions types (date, file upload, paid addons) implemented before passbook.
I was reviewing a number of old issues seeing what was mentioned and this one caught my interest in terms of your comment. It's great to know what is possible, and hope someone gets to develop it. I'm waiting for my clients to restart some events before being able to look to reinvest in development 😕
😁 Totaly agrees that there's probably more priority on other elements. One thing I'm thinking is. If there's a REST API like we can use, it would be very quick & easy to develop it without the need of knowledge on how Attendize works internally.
I think the Api is a work in progress - definitely not an area I know about. I can see this https://github.com/Attendize/Attendize/blob/23c2cf06b676ec59f349e078e8245e270e688893/routes/api.php and also a recent pull request #926 .
Still don't get how I should call it ? [url]/api/events ? Maybe it's just a WIP and should wait a bit more.
You are probably right unless others can give a more helpful guidance. I know someone created a flutter app which must have used the api - https://github.com/Attendize/Attendize/issues/467
Currently api is basically non-existent.
I'm doing an api for my project but it is far from where I can share it and it has many my business related stuff that is not part of this project.
What I would suggest if you would work on api for your app is to create new file in routes, and do all your routing there. Then import your file at the end of api.php. This way all your routes would be added to /api and you will have very little merging collisions.
IMO Ideally this project needs a graphql api which would be allowed to use from other servers using tokens. This way everyone can add functionality by just creating services that connect to that api.
