Originally Posted by
scubadu
I don't feel that everything under the sun needs a dedicated app. Frankly, if the functionality of the app requires that I need to be connected to the network, either via cellular or Wi-Fi means anyhow, then mobile.aa.com works fine for pretty much everything needed.
Yet another app means I have to download it from iTunes, keep it updated, sacrifice space on my phone, etc. It's a pain in the rear. I mainly only like apps that provide some kind of inherent value (particularly allowing one to do something "offline") that can't be done via a website, but I just don't think that is the case here. For any "real" functionality, you are going to need a network connection, and if you have a network connection then just access mobile.aa.com via the browser.
Interesting point. For on-line services (such as Facebook), a dedicated app usually is just a means for better UI than be easily done on a web page, since the app knows the semantic actions you can take.
However, your point about offline use applies here: a dedicated AA app could cache your itineraries, allowing access when not connected. If Apple were to relax the prohibition on apps running in the background, a dedicated app could stay up to date with gates and flight status.
Originally Posted by
captaink
I'd use the aa.com mobile site for the rest of my life if it meant I could have a flyertalk app...
Indeed, the mobile FT site is very clunky on a soft-key phone.