Updated README.md #458
Updated README.md #458
Conversation
| @@ -11,6 +11,18 @@ Welcome to Braintree's Drop-in SDK for iOS! | |||
|
|
|||
| **The Braintree iOS Drop-in SDK permits a deployment target of iOS 12.0 or higher.** It requires Xcode 15.0+ and Swift 5.9+. | |||
|
|
|||
| ## 📣 Announcements | |||
There was a problem hiding this comment.
Would it make sense to move the announcement to top of README?
There was a problem hiding this comment.
+1, we should put this up in lights as clearly as possible
There was a problem hiding this comment.
Maybe even some scary-looking alarm emojis, or things to grab people's eye.
What about also updating the repo description with some warning message?
There was a problem hiding this comment.
I was thinking about that since someone needs to scroll past the image to see the announcement
README.md
Outdated
| @@ -11,6 +11,16 @@ Welcome to Braintree's Drop-in SDK for iOS! | |||
|
|
|||
| **The Braintree iOS Drop-in SDK permits a deployment target of iOS 12.0 or higher.** It requires Xcode 15.0+ and Swift 5.9+. | |||
|
|
|||
| ## 📣 Announcements | |||
|
|
|||
| **The iOS Drop-In SDK is currently inactive and will be unsupported by November 2025**. As of December 2024, the iOS Drop-In SDK is inactive. No additional features will be added with the exception of security updates. As an alternative, we recommend using the  for unbranded checkout. | |||
There was a problem hiding this comment.
Nit / take it or leave it - instead of "recommend" (which suggests they maybe look to another provider) do we want to say something like
"Instead, implement a custom UI using braintree_ios"?
There was a problem hiding this comment.
Good point, will add that to be more specific
There was a problem hiding this comment.
Should I add that we are no longer addressing bugs? or leave it at "no additional features will be added"?
I changed the last sentence to say "Instead, implement a custom UI using the ." Open to feedback about the wording
Co-authored-by: Jax DesMarais-Leder <[email protected]>
Co-authored-by: Jax DesMarais-Leder <[email protected]>
|
Closing for now until team comes to conclusion about communication timelines |
Summary of changes
Checklist
Authors