2

I'm developing a social app, there is a main feature, "feeds".

so far It works with auto layout, everything is fine, but considering the cost of advanced development and maintenance in the future, I am looking for other async UI solutions.

I think ComponentKit, AsyncDisplayKit are what I looking for

but which one is better for me ?

both of them are supported async ui layout, and network image placeholder and cache ?

what's the difference between ComponentKit and AsyncDisplayKit ?

which one is better for complex feeds design ?

include : swift native / friendly, async ui layout, image cache & placeholder, complex feed style (horizontal cells in vertical cell) ... etc

PatrickSCLin
  • 1,419
  • 3
  • 17
  • 45

2 Answers2

2

Component Kit - Large Declarative (a lot of code by file) layouts without access to animation and frames. AsyncDisplayKit - Small, laconic, declarative layouts, if you override layoutSubview method you can block ASyncDisplayKit to calculate frame, and do yourself animation by direct access to the view's frame.

My choice AsyncDisplayKit its more friendly, easy to make, hard layouts in minutes.

Bimawa
  • 3,535
  • 2
  • 25
  • 45
0

I had been doing some research into both ComponentKit and AsyncDisplay kit and I think this post from Adam Ernst summaries it nicely:

AsyncDisplayKit enables complex gesture-driven animations, precisely the area that is a weak spot for Components. This makes the choice easy:

  • If you’re designing a complex gesture-driven UI, AsyncDisplayKit might be right for you.
  • If your interface looks more like Facebook’s News Feed, Components could be a good fit.
Iain Smith
  • 9,230
  • 4
  • 50
  • 61