Pedro Piñera

We redesigned our marketing site to match our dashboard and align with Noora's design system—creating a cohesive experience.

@asmitbm wrote about the motivation, design decisions, technical choices, and challenges we faced rebuilding it.

Read the story: https://tuist.dev/blog/2...

Debugging CI/CD pipelines locally was prohibitively complex & expensive to solve. AI coding tools changed that equation.

We built Magnolia—run GitHub Actions, GitLab CI, & Forgejo pipelines locally.

https://github.com/tuist...

Not complete, but open to contributions. No more push-pray-wait.

One day, AI models will remember that Tuist's domain is tuist.dev (not tuist.io and that "Tuist Cloud" doesn't exist.

Until then, we keep correcting the hallucinations.

We build Tuist with Tuist. And we made our dashboard public so anyone can see exactly what they'd get—no demos, no gatekeeping needed.

The traditional "book a demo" model is broken. Openness wins.

See our Xcode cache analytics: https://tuist.dev/tuist/...

No sign-up required.

At Tuist, localization means connecting with communities who love our tools.

Our Korean community has been with us since day one. That's why our new site is now in Korean, thanks to Youngjun Lee.

Watch the story: https://videos.tuist.dev...

감사합니다! 🇰🇷

Build systems & test runners are where production infrastructure was pre-Docker/Kubernetes.

The winning move isn't embracing fragmentation - it's creating the vendor-agnostic abstraction layer.

Infrastructure primitives for builds/tests that work regardless of toolchain. That's the unlock.

Codex has been an amazing partner building Tuist. We're shaping our product as two pieces: the tech and its hosting. Codex helps me figure out where to draw that line. Exploring infrastructure for modern build systems. Like having a technical co-founder always available to bounce ideas off.

Source-available is a productivity multiplier. Users debug issues and send PRs themselves. You shift from support to code reviewer. Conversations happen around code, not tickets. Trust is higher because devs see exactly how you work. No hiding, just real solutions in the open.

Xcode Cache analytics are slowly getting better. You'll soon be able to see more information about the cacheable tasks: https://github.com/tuist...

Coding agents writing tests often lean on global state (runtime or disk) that leaks between tests, causing flakiness and order-dependent results.

Solution: Keep global context reminding agents to scope state properly: temp directories, dependency injection, isolated test state.

Huge difference!

🇰🇷 또한, 귀사나 프로젝트, 사용 후기를 Tuist 웹사이트에 소개해도 괜찮으시다면 DM으로 알려주세요. 기꺼이 설정해드리겠습니다!

🇯🇵 また、もし貴社やプロジェクト、お客様の声をTuistのウェビサイトに掲載してもよろしければ、ぜひDMでお知らせください。喜んで設定させていただきます！

🇰🇷 Tuist 마케팅 사이트 한국어 번역에 참여해주세요!

멋진 한국 커뮤니티와 더 가까워지기 위해 새로운 마케팅 사이트를 한국어로 제공하고자 합니다.

도움을 주시는 분들께는 개인 프로젝트용 1년 무제한 액세스 권한을 드립니다!

자세한 내용은 여기👇
https://community.tuist....

#Tuist #iOS #한국어번역 #OpenSource

🇯🇵 Tuistマーケティングサイトの日本語翻訳にご協力ください！

素晴らしい日本のコミュニティの皆様により近づくため、新しいマーケティングサイトを日本語化したいと考えています。

ご協力いただいた方には、個人プロジェクト向けの1年間無制限アクセス権を提供！

詳細はこちら👇
https://community.tuist....

#Tuist #iOS #日本語翻訳 #OpenSource

🎯 Back Market shares why they migrated to Tuist

Results: 35-40% faster clean builds (90% with cache!), no Xcode freezing, better incremental builds, dynamic frameworks for dev.

Key insight: choose tools that fit your team's capabilities, not just the most powerful.

https://engineering.back...

🎯 Back Market shares why they migrated to Tuist

Results: 35-40% faster clean builds (90% with cache!), no Xcode freezing, better incremental builds, dynamic frameworks for dev.

Key insight: choose tools that fit your team's capabilities, not just the most powerful.

https://engineering.back...

Attio's flexibility seemed great at first, but doing sales as a founder made me realize it's too hands-on.

I need something that keeps conversations warm, nurtures accounts, and preps for renewals. Most of what I do could be a GitHub project.

Considering operate.so Anyone used it?

Just published: how CI/CD evolved from vendor lock-in to developer freedom.

Switching Mac runners? One line of code.

Interactive demo inside:
https://runs-on-mac.com

Just published: "runs-on: mac" - how CI/CD evolved from vendor lock-in to developer freedom.

Switching Mac runner providers? One line of code. GitHub Actions' unbundling created real competition.

https://runs-on-mac.com

Hot take: SwiftPM would be better with TOML/JSON/YAML + JSON schema instead of Package.swift.

Rust nailed this with Cargo.toml. Static config = no compiler slowness, better editor support.

Most Package.swift files are just structures anyway. Those doing I/O? Anti-pattern.

New post: How tiny design decisions can move an entire industry

From Mise to AI-assisted Bash scripts, small innovations are challenging years of assumptions in developer tooling.

https://pepicrft.me/a-ti...

Swift-build is good for unifying build systems, but fragmentation between Xcode projects & Swift Packages remains. Apple needs to decide the path forward instead of maintaining two graphs that need constant reconciliation. SPM's interface mixes dependency & project contexts badly.

Hot take: Coupling automation to CI pipelines is a liability. As coding environments evolve (Claude Code, Codex, etc.), pipelines should stay lean.

Tools like Mise: declare environment + tasks once. CI, LLMs, and local dev all interface with it.

Lean pipelines, portable automation.

We've improved Okta SSO in Tuist! You can now initiate authentication directly from the Tuist login page instead of going through your Okta portal first. Smoother workflow for your team. https://tuist.dev/change...

If you are maintainer of a Swift Package and would like to analyze and lint your package's graph, you might want to check out this new open source tool by the team at GetYourGuide
https://github.com/getyo...

At Tuist, we moved to continuous releases & a monorepo to ship changes quickly with a small team.

This lets us ship atomically, like Marek's Xcode cache analytics: https://github.com/tuist...

Our source-available setup means people can follow along and see how features are built.

Sold churros at my family's cafe as a kid. Forgot it all as a developer.

At Tuist, we answered questions but missed real pain conversations. Changed that. Listen, track with @attio.com, follow up with substance.

Founder-led sales works.

https://pepicrft.me/what...

B2B sales take time, but closing deals makes it worth it.

We've found our sweet spot: craftsmanship + hands-on work with engineering teams. Prospects love working directly with us - the builders.

How we present Tuist + active engagement = strong pipeline. Renewing and closing new accounts.

Elixir is full of useful gems. Just came across this one to capture logger outputs scoped to the test. Doing something like that in the Tuist CLI codebase took us a bunch of boilerplaity code:
https://hexdocs.pm/ex_un...

If Kotlin is doing multi-platform and Swift is doing multi-platform too, will we see iOS and Android team debates to push for their language onto the other platforms? 🤔