Ex-Amex, currently an indie developer working on Mooligan - A Magic the Gathering wiki app
🇲🇾🇸🇬
GitHub - https://github.com/missingems
I usually use a UUID as the id, and it works fine.
Other factors include the number of subviews, custom drawing, and images that affect performance.
We need a recycle view; it’s production proven.
I usually use a UUID as the id, and it works fine.
Other factors include the number of subviews, custom drawing, and images that affect performance.
We need a recycle view; it’s production proven.
For example, comparing using index as ID, a short unique string as ID, or an entire complex hashable struct as ID, the simpler your item identifier, the better it is performance wise.
This can be observed via profiling.
For example, comparing using index as ID, a short unique string as ID, or an entire complex hashable struct as ID, the simpler your item identifier, the better it is performance wise.
This can be observed via profiling.
And to me, stable FPS is more important. A decade-old iPhone X could scroll through a collection of photos without stuttering, but we couldn’t achieve the same with the latest tech is unacceptable.
And to me, stable FPS is more important. A decade-old iPhone X could scroll through a collection of photos without stuttering, but we couldn’t achieve the same with the latest tech is unacceptable.