Question 1

How do I add Public-Extension extensions to my iOS app?

Accepted Answer

You need to open the Swift Playground file in Xcode, copy the desired extensions, and paste them into your project's source files. There's no package manager support, so manual integration is required, which can be tedious for large projects.

Question 2

Is Public-Extension better than writing my own Swift extensions?

Accepted Answer

Public-Extension offers community-vetted code that can save time and introduce best practices for common tasks. However, for project-specific needs, custom extensions might be more appropriate, so it's best used as a learning tool or for boilerplate reduction.

Question 3

How often is Public-Extension updated?

Accepted Answer

New extensions are shared weekly via Twitter from @PublicExtension, with each tweet including sample usages and a link to the code in the repository, ensuring regular but informal updates.

Question 4

Can I suggest an extension to Public-Extension?

Accepted Answer

Yes, you can DM suggested extensions on Twitter with a GitHub gist, as mentioned in the README. This community-driven approach allows for contributions but depends on Twitter engagement.

Question 5

Public-Extension vs Swift Package Manager libraries for extensions

Accepted Answer

Public-Extension is great for discovery and experimentation in a playground, but SPM libraries offer better dependency management, versioning, and integration for production use. Choose based on whether you need informal learning or formal dependencies.

Question 6

Does Public-Extension work with SwiftUI?

Accepted Answer

The extensions cover Swift language features and common types, so they can be used with SwiftUI projects, but they are not specifically tailored for SwiftUI, focusing more on general Swift enhancements.

Public Extensions

What is Public Extensions?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions