3 ms·
"That's already a shot in the head for that method being anything resembling realistically efficient, in my opinion." I'm not sure. I've been thinking about th
by callmeed 18y ago
"That's already a shot in the head for that method being anything resembling realistically efficient, in my opinion."
I'm not sure. I've been thinking about this too for convention sales. If you've already got an online checkout form, why not just update it to detect the iPhone and render using an appropriate stylesheet?
If you have to mix two billing/merchant systems (because you have to use authorize.net for this), that's even more inefficient, IMO.
- ja2ke 18y agoI was almost entirely referring to mobile Safari's tendency to cache nothing ever. With an app like this, everything but the actual transaction data is stored locally, and the time you'd save from that could easily be the difference between accepting credit cards being worth it, or a too much of a hassle. Both in terms of potential consistency and responsiveness (no screen zooming in and out to enter data in a form field, for instance), and speed (no having to worry about having to wait between states other than actual card processing), having this software running locally as a native app instead of an optimized site, I think, have very tangible benefits given where this app would most likely be used. Man, wrote more than I meant to there. Whoops!