
GitHub
GitLab
BitBucket
openDesktop.org
Gitea
Launchpad.net
OSOR
The Complete Open-Source and Business Software Platform.

Apple Wallet
Pass2U Wallet
Passworks
Google Wallet
Developer-first REST API for Apple Wallet and Google Wallet passes. One POST returns a signed .pkpass and a Save to Google Wallet link. A PUT updates the pass and pushes to both wallets. No Apple Developer account or Google issuer setup.

Which is more popular?
Website, pricing, platforms and company facts side by side.
|
|
|
|
|---|---|---|
| Website | sourceforge.net | walletwallet.dev |
| Pricing | — | |
| Listed in |
In their own words, as submitted to SaaSHub.


No description of SourceForge yet.
WalletWallet is the simplest API for generating Apple Wallet and Google Wallet passes. One POST returns a signed Apple .pkpass, a Save to Google Wallet link, and a hosted page that shows the right Add button per device. There is no Apple developer account, certificate, or Google issuer setup:...
What each product offers, as listed by its team.


Possible disadvantages
An editorial look at what each product does well and who it suits.


Overall verdict
Why this product is good
Recommended for
Overall verdict
Why this product is good
Recommended for
Walkthroughs and reviews on video.
Presearch Privacy Review #27 - Sourceforge
More videos
No WalletWallet.dev videos yet. You could help us improve this page by suggesting one.
How often each product is chosen within a category, 0–100% relative to the other.


As answered by people managing SourceForge and WalletWallet.dev.
WalletWallet.dev's answer:
Developers and small teams adding wallet passes to a product they already run. Typical use cases are loyalty cards for cafes, gyms and shops, membership cards for libraries and studios, event and cinema tickets, season passes, coupons and gift cards. Agencies also use it to build white-label loyalty for their clients.
WalletWallet.dev's answer:
Hosted on Cloudflare Workers, so pass generation runs close to the caller worldwide. Updates are pushed to Apple over APNs and to Google over server-side push. The docs are also published in agent-readable form at walletwallet.dev/llms.txt, so a coding agent can wire up the integration.
WalletWallet.dev's answer:
You do not need an Apple Developer account or a Google Wallet issuer account. We run the signing and issuer infrastructure for both platforms, so you can ship a pass in your first hour instead of waiting on Apple to verify a developer account. One POST returns a signed .pkpass and a Save to Google Wallet link at the same time, and a pass that lands on both wallets counts once.
WalletWallet.dev's answer:
Three reasons. One call issues to both wallets, so you are not integrating Apple and Google separately, and a pass on both counts once. There is no certificate or issuer setup, because we sign and issue with our own. And the full lifecycle is covered: a PUT updates a live pass and pushes the change to every phone it is installed on, a DELETE revokes it. Pricing is flat at $39 a month for 100,000 passes, with a free tier at 1,000.
WalletWallet.dev's answer:
We wanted a few wallet passes for another project and hit the Apple Developer wall: $99 a year and a multi-step certificate setup before you can sign anything. The API providers around at the time still required you to bring your own developer account, so they saved you the code but not the setup. WalletWallet started as the missing piece: call one endpoint, get a signed pass back, no certificate work at all. Google Wallet support followed on the same principle, with no issuer account to create.
WalletWallet.dev's answer:
We don't publish customer names without their permission. The active base is small teams across these segments: - Cafes and small retailers running loyalty programs - Event organizers and venues issuing tickets - Agencies building white-label loyalty for their clients - Indie developers shipping a membership or ID card inside their own product
Share your experience with using SourceForge and WalletWallet.dev. For example, how are they different and which one is better?
External articles and on-site reviews we used to compare the two products.


SourceForge is a great place for people who like open-source software. It offers a strong platform where you can find, review, and handle software, all while helping the open-source community.
SourceForge’s user interface works fine, but it could do with a modern overhaul to make it easier on the eye and give it a more intuitive feel. While it has a large community, SourceForge’s support is not as extensive...
Sourceforge has been around longer than most, and it has the projects to prove it. Lots of open source Linux, Windows and Mac projects are hosted on SF. It has a totally different project structure when compared with...
We have no reviews of WalletWallet.dev yet. Be the first one to post
When comparing SourceForge and WalletWallet.dev, you can also consider the following products.

Originally founded as a project to simplify sharing code, GitHub has grown into an application used by over a million people to store over two million code repositories, making GitHub the largest code host in the world.
Compare GitHub to SourceForge or WalletWallet.dev:

With Wallet, you can keep your credit, debit, and prepaid cards, store cards, boarding passes, movie tickets, coupons, rewards cards, and more in one place.
Compare Apple Wallet to SourceForge or WalletWallet.dev:

Create, review and deploy code together with GitLab open source git repo management software | GitLab
Compare GitLab to SourceForge or WalletWallet.dev:


Bitbucket is a free code hosting site for Mercurial and Git. Manage your development with a hosted wiki, issue tracker and source code.
Compare BitBucket to SourceForge or WalletWallet.dev:

Effective consumer engagement to increase store traffic
Compare Passworks to SourceForge or WalletWallet.dev: