Skatan, we're implementing panning support because that's the only cross-platform solution there is. On iOS, my understanding is that you can only fetch the keyboard height when it has just been displayed. On Android, there is zero means of fetching the keyboard height, which doesn't help you from a cross-platform standpoint (the original poster attempted this and failed). So, this makes panning the winning solution. Especially since this is the solution that all native apps use on both iOS and Android anyways and is what Apple and Google recommend.