Stream-Framework VS stream-chat-swift

I have looked into a getstream.io integration, however it seems that the Ruby SDK is really treated as a second class citizen. There's bugs with the documented API (I'm having issues even creating users and querying users), the usage of the gem is low and there is an open issue since May that no one has even looked at, which doesn't give me hope for long term support.

An ultralight social media app with no dependencies that can run on shared web hosting. It's an API like Getstream, so F/E is up to you. I've had a fork of it in production for 2.5 years on a subscription site that generates a small income.

Now, I'm seeking your advice and opinions. If you have experience using Stream or MirrorFly for chat implementation, I'd greatly appreciate any insights you can provide. Here are some questions I have:

Think about the edge that you can have over thousands other people looking for a job like you. One of the ways to do it – tailor your (even small) experience to the company you are applying to. E.g. Let's take a company like Stream that have an open-source Swift SDK, try to contribute to their SDK, maybe close some `good-first-issue`s here and there, do some documentation improvements, enrich their example app. So that when you feel like you are ready to knock their door – you already have an edge over others – you don't need onboarding (because you already know most of their codebase, you even completed your first few tasks while yet not being employed!)

This is absolutely absurd. I mean I 100% believe it happens, it's just absurd that the Tier 1 admin bot is this bad.

I too firmly believe the tier 1 admins are just this program - https://getstream.io/ And reddit doesn't want to admit that humans are not actually reviewing things

Really depends on so many variables, and comes down to knowing the audience. I built a lightweight social network api platform to do a lot of what getstream.io and OSSN does, but the way users engaged with it was nothing like what I expected. One use case, for example, would have been mostly satisfied with WordPress and Mailchimp. Forums are very familiar to people and still used by a lot of "I don't do social media" types. At the risk of making a sweeping generalization, if you have an older target audience they will be happy with a forum. If you have a younger target audience they will prefer the sequential post / react style of interacting, like Discord or Instagram.

Cometchat's idiomatic SDKs are designed to help you build quickly. Available for iOS, Android, and web, they all work together, making cross-platform a breeze. With documentation that's best in class, in-depth tutorials, and demo apps for every platform, it is easier than ever to add 1:1 and group voice and video call functionality to your app.

Think about the edge that you can have over thousands other people looking for a job like you. One of the ways to do it – tailor your (even small) experience to the company you are applying to. E.g. Let's take a company like Stream that have an open-source Swift SDK, try to contribute to their SDK, maybe close some `good-first-issue`s here and there, do some documentation improvements, enrich their example app. So that when you feel like you are ready to knock their door – you already have an edge over others – you don't need onboarding (because you already know most of their codebase, you even completed your first few tasks while yet not being employed!)

Programming Languages: Swift, Kotlin, Java

We reached out to Alex Nagy, co-founder and CTO of Rebeloper, to learn if he could add chat to his iOS app in as little as five minutes using the Stream iOS Swift SDK.

In this article, we'll build an iOS chat application with Stream Chat, for its fully featured iOS chat components and Auth0's passwordless features for authentication.

Check out Stream on Github. They have a few chat SDKs for iOS, Android, React and a few others. Website: https://getstream.io/

It's also harder to write unit tests without the possibility of instantiating a mock instance of your class. The last point is not valid for Stream Chat Swift SDK's ChatClient, since its initializer is public to support the Dependency Injection pattern, which we'll discuss next.