📚 Documentation: How do you think about renaming the repository to "sdk-for-swift"

[dubiao]

💭 Description

I suggest renaming this repository to sdk-for-swift. This is because it is a SDK specifically created for the Swift language, which is an open-source language that can run on multiple platforms, not just Apple's platform. Therefore, changing the name can more accurately reflect the purpose of this SDK and provide clearer information for users. I hope you will consider this suggestion and make the necessary changes.

For example, another project named "sdk-for-kotlin," indicating that it is not only for server-side Kotlin but also for Android development.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[iMacHumphries]

Hey Appwrite team!

I just recently set up a Swift Runtime on a self-hosted server, and it's.... AWESOME!

I also just discovered the difference between sdk-for-swift & sdk-for-apple and I have some feedback:

1. 2 SDKs and the reason they are separate is not immediately intuitive - I first discovered the sdk-for-swift and didn't realize there were 2 separate frameworks.

• I later stumbled upon this repo and I assumed that one was just a legacy name change.
• During integration I was very confused when I tried to utilize the Account.create function from the server but it didn't exist within the SDK. I could see the function in Appwrite docs, but it took a while for me to figure out that it was in this repo.

2. This could be more flexible - I realize now that the intention seems to be that the client (sdk-for-apple) is intended to call the account creation endpoint, but I would appreciate the flexibility to have this happen server side.

Why server side account creation?

1. My client is written in an unsupported language (GDScript). Which means that I would need to use the REST API.
2. I don't like the idea of users generating UUIDs (also it's not as easy to create a uuid in GDScript).
3. I would like to (more easily) trigger other backend events/set up at the time of account creation on the server.

Please consider merging these libraries for simplicity. I would suggest:

1. 1 Repo for all things Swift - This would make it simple to find what I'm looking for & understand the separations.
2. 4 or 5 packages: AppwriteClient, AppwriteServer, AppwriteCore if you need it, AppwriteModels etc.. This would give really great flexibility while maintaining the separation of concerns.

I have other Appwrite-Swift newbie feedback that doesn't apply to this thread, so let me know if you're interested :D

[stnguyen90]

@dubiao, thanks for raising this issue! 🙏🏼 We have SDKs meant for client-side use and others for server-side use. You can find more information here. As such, we won't be combining.