Rename to iOS SDK

[jonathannorris]

I believe we should rename this from the swift-sdk to the ios-sdk. The reality is that this SDK only currently works on iOS, and its main intended use is for Apple's platforms (we should be able to add support for tvOS / visionOS / watchOS / macOS fairly easily). It also seems that most companies within the industry still use ios-sdk for a Swift SDK that supports other parts of the Apple ecosystem.

From a marketing perspective, iOS developers coming to OpenFeature are searching for an iOS Client SDK, we also already call this SDK the OpenFeature iOS SDK in our public documentation: https://openfeature.dev/docs/reference/technologies/client/swift

I am happy to help drive the changes to the repo name, documentation, and whatever else would be required. But I believe that because we are only using SPM, all that would be required is:

• Rename repo from swift-sdk to ios-sdk
• Update repo README.md and any other repo settings from swift-sdk to ios-sdk
• Update public openfeature.dev documentation

[beeme1mr]

I'm in favor of this. For what it's worth, the OpenFeature docs already refer to this as the iOS SDK. I think this just validates that naming is hard!

[nicklasl]

I support this as well.

One unknown on the SPM-part: Do we know if it supports redirects? I.e: will it break any current build pipelines?

  .package(url: "git@github.com:open-feature/swift-sdk.git", from: "0.3.0")

[jonathannorris]

I support this as well.

One unknown on the SPM-part: Do we know if it supports redirects? I.e: will it break any current build pipelines?

.package(url: "git@github.com:open-feature/swift-sdk.git", from: "0.3.0")

I'll test that out before we rename it.

[goranche]

I would advise against using iOS in the name, as one would think that will not be the only platform supported, and given the momentum Swift is gaining, I'd like to see this run on other platforms as well, at some point 🤷‍♂️