Big O Notation of your app

Even though you probably spent 5 years studying Computer Science and extensively using asymptotic notation, the truth is in the mobile development world there is a common myth about running time and space requirements being useless.

Modern devices are way more powerful for users to notice a difference between bubble sort and merge sort. Or not? Should everyone know how to implement Ukkonen's algorithm if they develop a weather app? What's the "Big O" of your average app and how to determine it?

I have answers to these questions and by the end of the talk you will have them too.