Xcode 12 is adding a new metric to objectively track how smoothly your app scrolls. This is kind of cool since scrolling smoothness feels right and is a sign of a good design.
Via iOS Dev Weekly.
Xcode 12 is adding a new metric to objectively track how smoothly your app scrolls. This is kind of cool since scrolling smoothness feels right and is a sign of a good design.
Via iOS Dev Weekly.
Retain cycles, timers, big images, caching. These are a few reasons why your app might be using more memory than it should.
It might be a good time to audit your app and see how much memory it’s really using.
Lazy loading, implementing memory warning methods, using NSCache, autorelease pools. These are a few ways to deal with it.
Also, let’s say, just make a clean, focused software design. π€·π»ββοΈ
Build-time optimization is not my favorite topic. It is truly not sexy. π€·π»ββοΈ I just want to write good code and run it without worrying about complier options and other distractions.
But I must admit that unless you love sitting around on your hands waiting to test your latest code change, this is good info to know. β±π€
This post explains exactly how to measure build times, target by target and task by task. Also, how to set up warnings for specific files taking a long time to process. You can even get a nice visual report like this:
π Xcode Build Time Optimization
And Part 2 gives you guidance on build settings optimizations, source code improvements, and project enhancements.
Via iOS Dev Weekly.
An interesting way to speed up your build/run/test cycle on big Swift projects.
π Barber: Fast build times for big Swift projects
Why compile your whole app and run the same steps to navigate to it every time you run when you’re just working on a single view controller or a smaller section of your app?
Via iOS Dev Weekly.