IOS Development recommends using LIB frequently

1. Mantle

Mantle allows us to simplify the model layer of COCOA and Cocoa Touch applications. Simply put. A network request is often made in the program, and the request is usually a JSON string. We usually build a model class to hold the data. This requires that we write a series of serialization code to convert the JSON to Model. This is a very time-consuming, easy mistake. Not easy to change. Mantle was very good at overcoming this problem. and easier to use.

• Github:https://github.com/mantle/mantle

• References:
  

  Tool article: Mantle
  Source code: Mantle

• Cocoapod integration: Pod ' mantle ', ' ~> 1.5.4 '

2. Masonry

In the IB era, it would be too low to assume that you are still using the code to absolutely layout.

With Apple announcing IPhone6, IPhone 6 Plus. IOS devices will have an increasingly rich screen size, and it's not possible to make a layout based on each size. So. It is necessary to use the AutoLayout.

In storyboard, it is easy to use AutoLayout. But in order to better collaborative development, some companies are still in the handwriting layout, it is frustrating that Apple provides AutoLayout syntax is obscure, it is very effective (you can dynamically view the AutoLayout syntax). Masonry is designed to solve complex handwritten autolayout. How to use AutoLayout gracefully, and see masonry.

• Github:https://github.com/masonry/masonry

• Reference: Use, please read the README

• Cocoapod integration: Pod ' masonry ', ' ~> 0.6.1 '

4. Blockskit

Blockskit is definitely objective-c's intimate companion, which provides a powerful Block syntax support for OC's often-used classes, making it comfortable, fast, and elegant to write OC code.

Anyway I was absolutely inseparable from it.

• Github:https://github.com/zwaldowski/blockskit

• References: Block usage summary, block in arc, how to prevent circular referencing (ZZ)

• Cocoapod integration: Pod ' blockskit ', ' ~> 2.2.5 '

5. Kvocontroller

Suppose you have a KVO in your project. Then Kvocontroller is definitely a good choice. It is a KVO enhanced framework for Facebook open source. There are several features:

• Use Blocks, define Actions yourself, or nskeyvalueobserving callbacks for notifications.

• No abnormalities when the viewer is removed

• Implicit viewer removal when controller Dealloc

• Improve performance with nskeyvalueobservinginitial

• Thread-safe and provides additional protection when the viewer recovers
  

• Is there any reason not to use Kvocontroller?

• Github:https://github.com/facebook/kvocontroller

• References: Kvocontroller:facebook open source KVO (Key-value observing)
  

• 
  
• 
  
• 
  
• 
  
• 
  

• 
  
  
  
  7. Odrefreshcontrol

• Very many companies are designing their own pull-down refresh view. For example, NetEase news IOS client. There will be advertisements when the drop is down. Suppose you just need a drop-down refresh, then you can consider Odrefreshcontrol, it is the original iOS6 on the rubber candy refresh style, very interesting. Today there are also a lot of apps in use, such as shrimp music and QQ client.

  
  

  • Github:https://github.com/sephiroth87/odrefreshcontrol
    

  • References

  • Cocoapod:pod ' Odrefreshcontrol ', ' ~> 1.1.0 '

  
  

  8. Pop

  
  

  Facebook is also open source. The famous pop, do animation is the perfect choice. Accept it.

  
  

  • Github:https://github.com/facebook/pop

  • Reference: Facebook Pop usage Guide popping (use instance of Pop)

  • Cocoapod:pod ' Pop ', ' ~> 1.0.7 '

  
  

  Cocoapod:pod ' Kvocontroller ', ' ~> 1.0.3 '

IOS Development recommends using LIB frequently