FlexLayout
Texture
| FlexLayout | Texture | |
|---|---|---|
| 1 | 4 | |
| 1,914 | 7,939 | |
| 0.8% | 0.3% | |
| 8.6 | 2.5 | |
| 2 months ago | 5 days ago | |
| Swift | Objective-C++ | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
FlexLayout
-
Building Reddit’s Design System on iOS
We still wanted to leverage a layout engine that could be performant and easy-to-use. After doing some performance testing with native UIKit, Autolayout, and a few other third-party options, we ended up bringing FlexLayout into the mix, which is a Swift implementation of Facebook’s Yoga layout engine. All RPL components utilize FlexLayout in order to lay out content fast and efficiently. While we’ve enjoyed using it, we’ve found a few touch points to be mindful of. There are some rough edges we’ve found, such as utilizing stack views with subviews that use FlexLayout, that often come at odds with both UIKit and FlexLayout’s layout engines.
Texture
-
Building Reddit’s Design System on iOS
Historically, Reddit has used both UIKit and Texture as layout engines to build out the Reddit app. At the time of its adoption, Texture was used as a way to build screens and have the UI update asynchronously, which mitigated frame rate hitches and optimized scroll performance. However, Texture represented a significantly different paradigm for building UI than UIKit, and prior to RPL, we had components built on both layout engines. Reusing components across these frameworks was difficult, and having to juggle two different mental models for these systems made it difficult from a developer’s perspective. As a result, we opted to deprecate and migrate off of Texture.
-
Telegram enable sign up without a SIM card
On iOS it’s written using a fork of Texture, formerly AsyncDisplayKit. In my experience, Texture outperforms UIKit’s auto layout and rich text widgets significantly.
https://github.com/TextureGroup/Texture
-
The SliceKit Series: Introducing Our New iOS Presentation Framework.
In order to make our engineers' lives easier and gain consistency in our user experience, we needed a declarative abstraction on top of UIKit. We chose UIKit because after experimenting with SwiftUI, Texture, ComponentKit, and other alternatives, UIKit offers us the right combination of features, including:
-
Ideas for research topic (thesis/dissertation) that includes iOS Development
Ok thanks. I've included a link for everyone else. Texture
What are some alternatives?
SnapKit - A Swift Autolayout DSL for iOS & OS X
IGListKit - A data-driven UICollectionView framework for building fast and flexible lists.
PinLayout - Fast Swift Views layouting without auto layout. No magic, pure code, full control and blazing fast. Concise syntax, intuitive, readable & chainable. [iOS/macOS/tvOS/CALayer]
ComponentKit - A React-inspired view framework for iOS.
LayoutKit - LayoutKit is a fast view layout library for iOS, macOS, and tvOS.
Atlas
Cassowary - A Swift port of the Cassowary linear constraint solver
SwiftyUI - High performance and lightweight UIView, UIImage, UIImageView, UIlabel, UIButton, Promise and more.
SwiftBox - Flexbox in Swift, using Facebook's css-layout.
Pulley - A library to imitate the iOS 10 Maps UI.
Masonry - Harness the power of AutoLayout NSLayoutConstraints with a simplified, chainable and expressive syntax. Supports iOS and OSX Auto Layout
AsyncDisplayKit - Smooth asynchronous user interfaces for iOS apps.