There's nothing "basic" about the core file manager/windowing system/explorer. It is one of the more complex processes, and will invariably grow since the poten

There's nothing "basic" about the core file manager/windowing system/explorer. It is one of the more complex processes, and will invariably grow since the potential feature set is near endless. An on screen keyboard doesn't have to be complicated, but once you add swype/multilanguage/dictionary/speech input/etc then it starts to require more IO to initialize. iOS was lag free pre-apps. Then people wanted apps, then legit multi-tasking, and then tons of services from the OS to support multi-tasking apps. Now you'll be running a dozen or more full time processes even excluding the kernel. > Is this a real hard problem to solve? It is an easy problem to solve. You'd just have to give up tons of features and functionality. > I would sacrafice, dedicated 20% of CPU/Memory, locked into these apps, so I never see slow down, when switching windows. That wouldn't help. Many things are IO bound not CPU/memory bound. Plus on mobile there is still the battery X factor. > Or is this not even an option to do? If so, why is it that the OS cannot reserve CPU cycles for itself that can never be touched by third party so it is always fast. Sure it can. Almost all operating systems allow you to set a process as high priority for scheduling. It just doesn't do much, because as I said it is IO bound not CPU bound, and plus sometimes processes are waiting for an atomic lock to come free and by prioritizing the process in the spin, you've actually slowed and delayed the process who needs to finish up and free the lock actually adding lag (this was a BIG problem on Windows in particular, which is why they actually split several kernel level atomic locks).