flagsmith-ios-client VS xcpretty

Glad you asked. Canary deployment, A/B testing, etc., processes were always limited to DevOps personnel. Now, tools like Flagsmith give this power to software engineers who can do it themselves with the clever use of feature flags.

Many companies choose to level up their feature flags and come to Flagsmith because they’re moving from a monolith to a microservice architecture. However, as engineers, we find ourselves moving in the monolith direction to support them. We even chose to build our monolith and write about that decision.

In this article we will discuss how we can combine the power of Vercel and feature flags (Flagsmith - open source) to build and deploy a config controlled application from scratch in less than 15 minutes using Next.Js feature flags.

There are however Saas to implement directly a feature management system. Several solutions exist like LaunchDarkly, Flagsmith or Unleash.io. Using a SaaS (Software as a Service) feature flagging solution offers the advantage of a faster and more straightforward implementation process. These services are readily available and can be quickly integrated into your project.

FlagSmith (Reasonably priced SaaS version)

This depends entirely on volume IMO. We [1] use Discord for this, and its great, but we don't have a large message volume. Discord seems way better than Slack for this use case as there's a single login which is built around connecting to multiple servers, unlike Slack.

[1]. https://www.flagsmith.com/

dependencies: [ .package(url: "https://github.com/Flagsmith/flagsmith-ios-client.git", from: "1.1.1"), ] If your project doesn’t contain a Package.swift file, go to the Menu bar in Xcode, select File, and then Add Packages. Then, in the search field, add the following URL:

I don't spend very much time in Xcode.

I try to use the command-line tools instead.

xcodebuild and xcrun are solid. check out xcpretty[^1] to improve the output of xcodebuild.

Here's a blog post that someone wrote about using xctest from the terminal with xcpretty to make the output nice: https://mokacoding.com/blog/running-tests-from-the-terminal/

[^1]: https://github.com/xcpretty/xcpretty