> Q: What *does* happen to a standard app run on the Xoom? Does it scale
> like on the iPad or does it actually run the app normally, just on a
> much bigger screen so you have a lot more whitespace and UI gaps? Or
> is the issue the added UIs for the new app management/task-switching
> and all tha
Agree on #1; this is how every iPhone/iPad app does it and so far the
iOS ecosystem seems to be doing just fine. I've rebought apps on my
iPad to get the "HD" versions of them and expected to repay; it was a
bummer, but I didn't lose sleep over it. I think the analogy to DVD/
Blu-ray was pretty muc
Maybe it depends by your application, but i think it is better #1.
You have to manage 2 different applications: phone version and tablet
version.
Consider environments: you can read football news on your mobile phone while
your are on bus. Usually you use tablet in office or at home, so your are
si
In many ways, using the compat framework makes me a little nervous. The
ApiDemo I looked at had an overarching Activity that managed two fragments
and while it was a simple example and only had a few "is landscape, do two
fragments, else, do one", I can imagine a real world app being far more
comp
On Sat, Mar 19, 2011 at 12:48 PM, Chris Stewart wrote:
> Anyone have any comments on this quote from me?
>
> "I do think it's important to note that if you follow approach #1, users
> that purchased your app will still have access to it on the tablet, it just
> won't be tailored to that device's e
Anyone have any comments on this quote from me?
"I do think it's important to note that if you follow approach #1, users
that purchased your app will still have access to it on the tablet, it just
won't be tailored to that device's experience. I'm not sure that asking
them to pay for the addition
Thanks for the replies. It's interesting to see how different devs are
handling this.
I do think it's important to note that if you follow approach #1, users that
purchased your app will still have access to it on the tablet, it just won't
be tailored to that device's experience. I'm not sure th
For a game, #1 probably makes more sense. For a productivity app for
which the user had already paid $10 for, #2 probably is a better
option, unless you want to piss off your users.
On Mar 18, 4:00 pm, Christer Nordvik wrote:
> I am thinking about #1 since you can always slap on a HD at the end
Sent from my Motorola phone.
Christer Nordvik wrote:
>I am thinking about #1 since you can always slap on a HD at the end
>like "Angry App HD" and charge the users more. At least that's the
>standard practice on iPad. But then you have to have some extra
>features (or just better graphics) on
I
TSent from my Motorola phone.
Christer Nordvik wrote:
>I am thinking about #1 since you can always slap on a HD at the end
>like "Angry App HD" and charge the users more. At least that's the
>standard practice on iPad. But then you have to have some extra
>features (or just better graphics) o
I am thinking about #1 since you can always slap on a HD at the end
like "Angry App HD" and charge the users more. At least that's the
standard practice on iPad. But then you have to have some extra
features (or just better graphics) on the HD version of your app.
My main problem is that the Xoom
I am going with route #2, and I haven't had too many problems up till
now. The major stumbling block I see in the business side of things
is that I cannot charge more for a Tablet version than I can for the
phone version, even though the usuability can be much greater on the
tablet version.
Optio
12 matches
Mail list logo
