Open-source project
TextureGroup/Texture avatar
TextureGroup/Texture

Texture: thread-safe nodes for iOS interfaces, and a rename still visible in the build files

Smooth asynchronous user interfaces for iOS apps.

8,180 stars1,310 forksObjective-C++NOASSERTION

At a glance

What is it?
The iOS UI framework that treats a node as a thread-safe abstraction over a view, so image decoding, text sizing, layout and rendering can happen off the main thread. It arrives through CocoaPods or Carthage, its Xcode project is still named after the old AsyncDisplayKit name, and its newest tag is 3.2.0 from 2024.
Who is it for?
It suits an iOS team with interface work that drops frames, especially list and collection screens where cell reuse bugs and preloading dominate the complaints. It does not suit a team starting a new SwiftUI project, since this is an earlier-generation UIKit-era framework and the README frames it as a replacement for AsyncDisplayKit rather than a modern default.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly Objective-C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • TextureGroup/Texture8,180 ★ · +0
Star history
Repository2026-09-222026-11-15
TextureGroup/Texture8.2k8.2k

0 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Nodes are thread-safe and views are not

The whole argument of the framework is in one abstraction. Texture's basic unit is the node, and an ASDisplayNode is an abstraction over UIView, which is in turn an abstraction over CALayer. Unlike views, which can only be used on the main thread, nodes are thread-safe, so entire hierarchies of them can be instantiated and configured in parallel on background threads. That is a different programming model from building views, not an optimisation pass on top of one: the construction of the interface stops being main thread work, so the thread stays available for user interaction while the expensive parts happen elsewhere. The README also frames this in terms of the problems developers actually recognise, naming cell reuse bugs and the need to preload data performantly for page and scroll style interfaces as the situations the framework is meant to rescue.

The real budget is ten milliseconds, not sixteen

The performance section does the arithmetic for you, and it is worth reading twice because the headline number is generous. To keep the interface smooth and responsive, an app should render at 60 frames per second, described as the gold standard on iOS. That gives the main thread one sixtieth of a second to push each frame, which is 16 milliseconds to execute all layout and drawing code. Then the correction: because of system overhead, your code usually has less than ten milliseconds to run before it causes a frame drop. Texture's contribution is moving image decoding, text sizing and rendering, layout, and other expensive UI operations off the main thread. So when you profile with Texture, the number to hold yourself to is ten milliseconds, not sixteen, and a screen that fits the sixteen millisecond budget can still drop frames.

The Xcode project is still called AsyncDisplayKit

Texture was previously known as AsyncDisplayKit, and the rename did not reach every file. The repository's build artefacts keep the old name: there is an AsyncDisplayKit.xcodeproj directory and an AsyncDisplayKit.xcworkspace directory at the top level, sitting next to the current podspec. There is also a ThreeMigrationGuide.md and a SubspecWorkspaces directory. For a newcomer this is disorienting rather than fatal, but it does mean the project you open is not named after the framework you installed. The build is scripted as well, with a build.sh at the root, a Podfile, a Cartfile with a resolved counterpart, a Schemas directory, a CI directory and a .ruby-version file for the tooling around it.

Two package managers, and Carthage builds the framework yourself

Installation is available through CocoaPods or Carthage, and the details live in an installation guide on the project site rather than in the repository. The two routes are not equivalent in effort. With CocoaPods you consume the pod, and the repository carries Texture.podspec. With Carthage, the repository carries a Cartfile with a committed Cartfile.resolved. Both are iOS-native distribution channels, so there is no package manager path here for a Swift Package Manager based project, and the README does not mention one. If your project already standardises on one of these two, this is a non decision.

code
Texture.podspec
Cartfile
Cartfile.resolved
Podfile
ThreeMigrationGuide.md

The examples directory is where the learning actually happens

There are more than twenty sample projects in the examples directory, and their names describe the problems the framework is built for. Basic ones sit alongside hard ones: ASViewController and Kittens for the fundamentals, PagerNode for paging, HorizontalWithinVerticalScrolling and VerticalWithinHorizontalScrolling for nested scroll behaviour, SocialAppLayout and its inverted variant for feed style layout, CustomCollectionView and ASCollectionView for list work, AnimatedGIF and Videos for media nodes, and LayoutSpecExamples for the layout specification system. Several exist twice, once in Objective-C and once suffixed with Swift, which is the clearest signal that the project is maintained for Swift teams rather than only for the language it started in. There is also an examples_extra directory, a smoke-tests directory, and an InstrumentsTemplates directory for profiling.

The newest tag is from 2024 while the branch keeps moving

The release history sets the expectation. Version 3.0.0 was published on 2020-07-15, 3.1.0 on 2021-09-16, and 3.2.0 on 2024-05-21, so the gap between the two most recent tags is nearly three years, while the last push to the master branch is dated 2026-10-30. Work is therefore happening on the branch between releases rather than in a steady release train, which is worth knowing if you are deciding between pinning a tag and tracking master. The process is written down rather than tribal: a RELEASE file at the root describes the release process, a CONTRIBUTING file covers how to get involved, and the changelog is maintained in the tree with a changelog generator configuration beside it. Documentation lives on the project site, with a getting started guide and a generated API reference.

Support is a Slack invitation, and the licence is stated loosely

Getting help is arranged around one channel. Slack is used for real time debugging, community updates and general discussion about Texture, and joining is by invitation: there is a self sign up link, or you can email the project's address to request an invite. That is a small thing, but on a framework whose hardest problems are layout and threading ones, synchronous debugging with maintainers is the resource that matters. The licence is described in the README as free use as described by the licence file, with Apache 2.0 named in that sentence, while the repository's own metadata records no standard licence identifier. If your organisation needs a confirmed SPDX identifier rather than a description, the licence file is where you resolve it.

Editorial conclusion

It suits an iOS team with interface work that drops frames, especially list and collection screens where cell reuse bugs and preloading dominate the complaints. It does not suit a team starting a new SwiftUI project, since this is an earlier-generation UIKit-era framework and the README frames it as a replacement for AsyncDisplayKit rather than a modern default. Check four things before adopting it: which package route you will take, because CocoaPods and Carthage have different build consequences, which Xcode project you are opening given the workspace is still named for the old project, which release you will pin, since the newest tag is from 2024 while the branch has moved since, and whether your codebase is prepared for an Objective-C++ component in an otherwise Swift project.

Frequently asked questions

What is Texture, and what happened to AsyncDisplayKit?

Texture is the current name of the project, and the README links a Pinterest Engineering article introducing Texture as a new home for AsyncDisplayKit. The old name survives in the repository's build artefacts, where the Xcode project and workspace directories are still called AsyncDisplayKit, and the repository includes a ThreeMigrationGuide.md.

How do I install Texture in an iOS project?

Through CocoaPods or Carthage, with the instructions in the installation guide on the project site. The repository carries Texture.podspec with a sub-specification workspaces directory for the CocoaPods route, and a Cartfile with a committed Cartfile.resolved for the Carthage route.

Why would I use Texture instead of plain UIKit views?

The stated argument is about the main thread budget: at 60 frames per second the main thread has 16 milliseconds for layout and drawing, and after system overhead your own code gets less than ten milliseconds before it drops a frame. Nodes are thread-safe, unlike views, so image decoding, text sizing and rendering, and layout can run on background threads.

Is Texture still being worked on?

The last push to the master branch is dated 2026-10-30. The tagged releases are 3.2.0 published on 2024-05-21, 3.1.0 on 2021-09-16, and 3.0.0 on 2020-07-15, so releases are spaced far apart while work continues on the branch between them.

Official sources

  1. Issues
  2. Project website
  3. README
  4. Releases
  5. TextureGroup/Texture on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/texturegroup-texture.svg)](https://hysenlabs.com/projects/texturegroup-texture)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/texturegroup-texture.svg)](https://hysenlabs.com/projects/texturegroup-texture)

Was this useful?