2 ms·
> I would suck it in and get down to the platform's assembly language layer which for IOS is ObjectiveC and for Android is Java. That only makes sense if the g
by golergka 10y ago
> I would suck it in and get down to the platform's assembly language layer which for IOS is ObjectiveC and for Android is Java.
That only makes sense if the graphnics performance is actually the bottleneck of your game.
99% of the games I've seen have game design as the weakest link though, and sometimes art (it's not amount of polygons on the screen — it's how beautiful those polygons are). And if you actually want to improve on your game design, the metric you have to optimize is iteration speed — and the "assembly language layer" is rarely the best for this purpose.