iOS Weibo UI instance-quasi-materialized design (not completely successful)

iOS Weibo UI instance-quasi-materialized design (not completely successful)

Introduction: Recent learning of the iOS Weibo UI instance, about UITableView learning, and then just see Google's material design about the Android interface of the quasi-materialized, whether it is the layout or color collocation is really good, Then just see a UITableView-like interface:

Because I not only like the code, but also like the UI design, so I think about this iOS aspect of the micro-blog UI instance, to imitate Google's Android design, and as far as possible not to use the design of the picture background (in fact, to find that can be fully implemented in the code to materialize).

The entire project, from the custom UI to the planning design of the entire project, knows that there are some limitations behind the discovery of cell and layout customizations via Xib or storyboard. The built-in technology provided by Apple is that the iOS system gets the height based on the layout of the cell's child control, and its limitation is that the maximum cell height must be returned based on the height of the child control that determines the frame, whereas in my instance, in order to have a single object in each cell background, I added a cell, which acts as a pseudo-background, actually a control, which obviously occupies the largest frame, but the height of the pseudo-background control cannot be determined because it must automatically be laid out and changed automatically based on other determined controls. The best way to do this is to redesign the frame with a purely code design. While pure code is rough and cumbersome, it is also the most flexible way. Because of time, there is no realization, there is time to give.

Directly below the source code download

iOS Weibo UI instance-quasi-materialized design (not completely successful)