Casey Liss

And what I really want is a deep dive about, okay, here's the reason this is the way it is. You might have family sharing or you might not. You might be entitled via family sharing or you might not. You might be entitled via family sharing and your own entitlement or you might not. You might be entitled via family sharing something else and your own entitlement, or you might not.

And what I really want is a deep dive about, okay, here's the reason this is the way it is. You might have family sharing or you might not. You might be entitled via family sharing or you might not. You might be entitled via family sharing and your own entitlement or you might not. You might be entitled via family sharing something else and your own entitlement, or you might not.

Or the family sharing has expired, but your own entitlement hasn't, or vice versa. And so suddenly you realize, oh no, I really do need to do the work of traversing all of these arrays of subscriptions and information and whatnot. But you come upon that oftentimes by users reporting into you, your app doesn't say it's purchased, but here's a receipt showing I purchased it.

Or the family sharing has expired, but your own entitlement hasn't, or vice versa. And so suddenly you realize, oh no, I really do need to do the work of traversing all of these arrays of subscriptions and information and whatnot. But you come upon that oftentimes by users reporting into you, your app doesn't say it's purchased, but here's a receipt showing I purchased it.

And that's not frigging helpful, Apple. That's too late. It's too late at that point. And that just drives me bananas. Another great example of this is I've started adding widget and intent support to call sheet. It hasn't shipped yet. But one of the things you can do is with widgets, I'm pretty sure it's widgets, you can communicate between the widget and the main app.

And that's not frigging helpful, Apple. That's too late. It's too late at that point. And that just drives me bananas. Another great example of this is I've started adding widget and intent support to call sheet. It hasn't shipped yet. But one of the things you can do is with widgets, I'm pretty sure it's widgets, you can communicate between the widget and the main app.

And there's not really a good overview page of your different techniques of doing this. And I pieced together that, oh, you can do like URL schemes, but it has to be a secure URL. It can't be like an X callback style URL. And I forget there was one other, oh, you can put things in user defaults, but even Apple seems to think like, I wouldn't recommend that if you're going to avoid it.

And there's not really a good overview page of your different techniques of doing this. And I pieced together that, oh, you can do like URL schemes, but it has to be a secure URL. It can't be like an X callback style URL. And I forget there was one other, oh, you can put things in user defaults, but even Apple seems to think like, I wouldn't recommend that if you're going to avoid it.

And that's, I thought that's all there was. And come to find out, there's actually, you can flip a switch. There's a Boolean somewhere in your widget where you can say, no, I need you to open the app when the widget is interacted with. And at that point, you're effectively in the app's runtime, and you can do kind of whatever you want.

And that's, I thought that's all there was. And come to find out, there's actually, you can flip a switch. There's a Boolean somewhere in your widget where you can say, no, I need you to open the app when the widget is interacted with. And at that point, you're effectively in the app's runtime, and you can do kind of whatever you want.

But there's no good overview of, okay, here are all of the available options, and here's why you would choose each one. It's not useless, but it's almost useless. And in some ways, it's worse than useless because they give you just a little nugget of information and then basically say... Have fun.

But there's no good overview of, okay, here are all of the available options, and here's why you would choose each one. It's not useless, but it's almost useless. And in some ways, it's worse than useless because they give you just a little nugget of information and then basically say... Have fun.

Thanks. That's helpful.

Thanks. That's helpful.

It's brutal, and I can't stress enough. It is light years better than StoreKit 1. I know I've said it two or three times. It totally is. I want to say it two or three more times. It is so much better than StoreKit 1, but it is still a lot.

It's brutal, and I can't stress enough. It is light years better than StoreKit 1. I know I've said it two or three times. It totally is. I want to say it two or three more times. It is so much better than StoreKit 1, but it is still a lot.

And some of that, maybe even most of that, is the domain that they're trying to cover because there's so many gotchas and what-ifs and this and that and the other thing. But again, it would be so much better if there was better documentation that walked you through, okay, here's the plain vanilla version where, you know, you have a single in-app purchase that's unlocking your app.

And some of that, maybe even most of that, is the domain that they're trying to cover because there's so many gotchas and what-ifs and this and that and the other thing. But again, it would be so much better if there was better documentation that walked you through, okay, here's the plain vanilla version where, you know, you have a single in-app purchase that's unlocking your app.

Okay, now what if you had a single subscription that unlocks your app? Okay, now what if you had multiple different in-app purchases that could unlock your app in multiple different subscriptions? Well, okay, now let's introduce consumables, you know, and build... step-by-step over all of these different problem domains, if you will. But there's just not that.

Okay, now what if you had a single subscription that unlocks your app? Okay, now what if you had multiple different in-app purchases that could unlock your app in multiple different subscriptions? Well, okay, now let's introduce consumables, you know, and build... step-by-step over all of these different problem domains, if you will. But there's just not that.