0dj0bz

To be clear, even our iOS app doesn't currently have a mechanism to sign up for the service; we reserve that for the website. On there, we support Apple Pay as a payment method via Stripe.

My fear is that they are going to try to force us to implement in-app purchases for the iOS app to register for the service, which I don't like because I just don't.

They are requiring us to implement Apple Pay as the only mechanism for signing up for an app subscription, even though there is no mechanism in the Safari extension to sign up. It seems like they want us to get rid of the links in the extension to take them to the web app to register and pay for the service, which would require it to almost be its own "Apple" version of the system. When we ask for clarification, we get the same boilerplate response no matter what we ask.

So you're building a SaaS app, or maybe you're just curious about how all those cloud services you use actually work behind the scenes. Either way, you've probably heard the term "multi-tenant architecture" thrown around. Let's break down what that actually means and why it matters.

When I was in my teens, I spent my summers rebuilding a LOT of Addressograph-Multigraph and (later) Farrington plate printing and embossing equipment. Some of this gear was impressive, either because of its mass (the big cast iron tag printers that were on pretty much every US Navy ship and military base) or its novelty at the time (the 6300 electronic card & plate embossers that were interfaceable to mini and mainframe computers). Learning the mechanical and electrical work on these machines made me a better engineer once I got to college.

Good point that it's also a credential. So I probably end up using a password manager almost as a "dictionary" to keep track of all of my aliases.

Thanks for the input.