I don't like it. Covering and uncovering the keyboard or screen mid-program is poor UX IMO. The keyboard is too big of an object on screen, too obvious, in an

I don't like it. Covering and uncovering the keyboard or screen mid-program is poor UX IMO. The keyboard is too big of an object on screen, too obvious, in an unhelpful way. Why not hide the keyboard, grey out your input box and refuse to take anything new until done processing and doing whatever it needs to do? Or move to a new view that has your information? And a loading box over the screen itself? Showing, hiding partially and then showing the exact same screen with little new information doesn't make sense and will confuse some users. If you're doing an app for a website (as far as I can tell, this is the main reason why a Loading view would pop up very often), why not look at Safari's Web Apps. They are still very good to use, and in some cases, will end up being much better then a native app would have been. Not to mention, you can distribute it however you like and not have to worry about the App Store.