Sebastian Aaltonen on Twitter

“Thus our solution for fast rendering on low/mid tier Android phones (50% of the market today) is to lean on traditional draw calls. Make draw calls as fast as possible on both CPU and GPU side. Well optimized solution can push 10,000 draw calls at 60 fps on 99$ Android phone.”

Twitter
@StompyRobot Yeah, wish we could convince @sebbbi to join us. His posts are one of the few reasons why I still lurk there once in a while.
@StompyRobot @sebbbi To add something useful to that thread: I think position shaders were first introduced by nvidia on Fermi, much earlier than Intel Xe! It was completely transparent and I don't think it was advertised much, so most devs were unaware of it.
@castano @StompyRobot @sebbbi We also did this in LRB FWIW.
@castano @StompyRobot The default path was for only positions + clip/cull dists to get evaluated for binning/FE work, and then attribute shading was way back in the backend (in "VPhase" _after_ rast and Z test [as long as early Z was on])
@castano @StompyRobot in particular verts only contained in tris that fully failed the depth/stencil tests never got shaded at all