Open cliftonlabrum opened 4 years ago
Hi @cliftonlabrum , this isn't something that's currently on our roadmap, but definitely something we could consider if there is sufficient demand for it -- particularly when we make the decision to start developing in Swift :)
(in the meantime we have added support for Catalyst if that help to unblock you at all) https://github.com/stripe/stripe-ios/issues/1364
I was hoping to use Stripe for my macOS app, alas. So count me as a +1
My workaround for this is going to be a webview or webpage that opens and the users signs up/purchase from that webpage with Stripe.
Adding a +1 here š
equally exploring offloading payments to web as a workaround but would love to keep it all in one place!
Also adding a +1 :)
Same +1
In this comment about SwiftUI support they mention the intention to "provide native SwiftUI support or SwiftUI wrappers for all future UI surfaces".
I wonder how the Stripe team would feel around an effort to migrate all UIView's to native SwiftUI and surface UIKit wrappers for backwards compatibility?
The native SwiftUI code would enable the Swift SDK to quickly and easily add support for macOS, tvOS and any future expansions (shopping in Apple's reality headset anyone? š)
It's unlikely to require huge rewrites to add SwiftUI (and by extension macOS) support to the core library. The other targets could be converted over time?
+1, mark!
I wonder how the Stripe team would feel around an effort to migrate all UIView's to native SwiftUI and surface UIKit wrappers for backwards compatibility?
I'd love to try that, but SwiftUI is still a little rough, especially considering the behavioral differences between iOS 13, 14 and 15. We're wary of using it in any SDK UI at this time, but we're looking forward to adopting it in the future!
+1
+1
+1
+1
+1
+1
+1
With KMM this would be really helpful
+1
I also need this
+1
Curious Any updates on this? Its been 4 years now!
@ajram23 I ended up using Lemon Squeezy API with my macos app for license activation & validation.
I downloaded iOS code and removed all references of UIKit, and then I utilised it for macOS, and it worked.
@KMSoft2013 you should put out a fork for the rest of us to use.
@KMSoft2013 you should put out a fork for the rest of us to use.
+1
I downloaded iOS code and removed all references of UIKit, and then I utilised it for macOS, and it worked.
Iām about to do the same and go on the rabbit hole! Iād you could hmsgare your code would be a massive time saver! š
+1
I will create separate fork and provide that.
Do you have any plans to support macOS with this SDK? I'm referring to a full Mac version, not just Catalyst support.
Even if you didn't provide any payment UIs, just having the API calls available in a Mac app would be great. Perhaps you could consider this as part of your efforts to create a Swift version (see https://github.com/stripe/stripe-ios/issues/1436).
Thanks! š