[android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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 much spot-on; if you want two copies, go for it. 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 that? On Mar 19, 2:42 pm, Alessio Grumiro a.grum...@gmail.com wrote: 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 sitted, no noise, more concentration. No consider if your user has, already, payed for phone version. 2011/3/19 Chris Stewart cstewart...@gmail.com 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 complicated to migrate to that model. I'm curious how many have taken the approach of having both modes in one app. I would love to hear some experiences from having made this migration to the compat framework. On Mar 19, 2011 4:10 PM, TreKing treking...@gmail.com wrote: On Sat, Mar 19, 2011 at 12:48 PM, Chris Stewart cstewart...@gmail.com 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 experience. I'm not sure that asking them to pay for the additional work you put into a tablet version is a bad thing. It works that way on the iPad, with no issues. I think having a separate tablet version that costs more, if that's what you want to do, is fine. It's like selling a DVD and BluRay copy of a movie - same product, different platform, where one costs more because it's bigger and better. If you want both, you have to pay for both. And if user is *really* unhappy about this, you can just refund their original phone version purchase and have them keep the tablet version, so they're only paying the difference (as was mentioned earlier) for the upgrade. Do it, go. --- -- TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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 that? It will scale it up to the full screen size of your device, which leads to a lot of whitespace in most apps including mine. -- Chris Stewart http://chriswstewart.com On Sun, Mar 20, 2011 at 10:18 AM, Riyad Kalla rka...@gmail.com wrote: 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 much spot-on; if you want two copies, go for it. 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 that? On Mar 19, 2:42 pm, Alessio Grumiro a.grum...@gmail.com wrote: 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 sitted, no noise, more concentration. No consider if your user has, already, payed for phone version. 2011/3/19 Chris Stewart cstewart...@gmail.com 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 complicated to migrate to that model. I'm curious how many have taken the approach of having both modes in one app. I would love to hear some experiences from having made this migration to the compat framework. On Mar 19, 2011 4:10 PM, TreKing treking...@gmail.com wrote: On Sat, Mar 19, 2011 at 12:48 PM, Chris Stewart cstewart...@gmail.com 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 experience. I'm not sure that asking them to pay for the additional work you put into a tablet version is a bad thing. It works that way on the iPad, with no issues. I think having a separate tablet version that costs more, if that's what you want to do, is fine. It's like selling a DVD and BluRay copy of a movie - same product, different platform, where one costs more because it's bigger and better. If you want both, you have to pay for both. And if user is *really* unhappy about this, you can just refund their original phone version purchase and have them keep the tablet version, so they're only paying the difference (as was mentioned earlier) for the upgrade. Do it, go. --- -- TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To
Re: [android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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 additional work you put into a tablet version is a bad thing. It works that way on the iPad, with no issues. I'm really quite curious. I think it's a big deal right now as the Android tablets are in their infancy and this market is just beginning. -- Chris Stewart http://chriswstewart.com On Fri, Mar 18, 2011 at 9:41 AM, Chris Stewart cstewart...@gmail.comwrote: 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 that asking them to pay for the additional work you put into a tablet version is a bad thing. It works that way on the iPad, with no issues. I'm leaning more towards option #2, but I'm a little worried about managing the different views in a single application. -- Chris Stewart http://chriswstewart.com On Fri, Mar 18, 2011 at 5:10 AM, Zsolt Vasvari zvasv...@gmail.com wrote: 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 cnord...@gmail.com 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 the HD version of your app. My main problem is that the Xoom doesn't give the tablet-only apps any special treatment so it will probably be drowned in other apps and doesn't take advantage of current rankings of your app. -Christer On Mar 18, 5:44 am, Zsolt Vasvari zvasv...@gmail.com wrote: 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. Option #1 is not the best, as you pointed out, you cannot force the users to pay twice. I can see forcing them to pay the difference in price if they upgrade to a tablet, but to make them buy the app all over is a huge no-no and you would end up with some very unhappy users -- and rightfully so. I think there needs to be a way to set price points based on the form factor of the device. Hopefully, the Amazon market will have this feature. On Mar 18, 12:13 pm, Chris Stewart cstewart...@gmail.com wrote: Now that I'm working on a tablet-centric version of my app, I'm considering how it will impact my existing application in the Market. As far as I can see it, there are two ways this can go: 1) Leave your existing app as-is in the Market. Build a tablet version taking full advantage of Android 3.0, setting your minSdk to 11, using your existing code base (as applicable) as a library to share core code, and sell the apps independent of each other. Here you'll need to manage two code bases, even if only the UI side which we all know varies greatly from app to app. You're also requiring users to purchase twice effectively, assuming they want the app on both their phone and the tablet-centric version on their tablet. I guess the phone version would still work on the tablet, just not optimized for it. 2) Integrate fragments into your existing application and bundle in the tablet version along with the phone version. You'll need to drop support for Android 1.5 for the compatibility library, work around API differences between the phone and tablet APIs at run-time, and handle your UI activities and views differently between platforms. I'm not sure about that last part -- but it seems like with such a different UI concept behind 3.0 with the Action Bar and the general flow of an application can be so different, that you might need to break that apart. Could be very wrong there however and would love for someone to show me otherwise. There are a few things at play here. It's the battle on the technical side of dealing with different applications (package names, projects in Eclipse, apks, etc). It's also bringing into question how you want to manage your app; whether you want to charge for a tablet-optimized version or include it with the phone app someone has already purchased. Depending on what I learn related
Re: [android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
On Sat, Mar 19, 2011 at 12:48 PM, Chris Stewart cstewart...@gmail.comwrote: 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 additional work you put into a tablet version is a bad thing. It works that way on the iPad, with no issues. I think having a separate tablet version that costs more, if that's what you want to do, is fine. It's like selling a DVD and BluRay copy of a movie - same product, different platform, where one costs more because it's bigger and better. If you want both, you have to pay for both. And if user is *really* unhappy about this, you can just refund their original phone version purchase and have them keep the tablet version, so they're only paying the difference (as was mentioned earlier) for the upgrade. Do it, go. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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 complicated to migrate to that model. I'm curious how many have taken the approach of having both modes in one app. I would love to hear some experiences from having made this migration to the compat framework. On Mar 19, 2011 4:10 PM, TreKing treking...@gmail.com wrote: On Sat, Mar 19, 2011 at 12:48 PM, Chris Stewart cstewart...@gmail.com 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 experience. I'm not sure that asking them to pay for the additional work you put into a tablet version is a bad thing. It works that way on the iPad, with no issues. I think having a separate tablet version that costs more, if that's what you want to do, is fine. It's like selling a DVD and BluRay copy of a movie - same product, different platform, where one costs more because it's bigger and better. If you want both, you have to pay for both. And if user is *really* unhappy about this, you can just refund their original phone version purchase and have them keep the tablet version, so they're only paying the difference (as was mentioned earlier) for the upgrade. Do it, go. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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 sitted, no noise, more concentration. No consider if your user has, already, payed for phone version. 2011/3/19 Chris Stewart cstewart...@gmail.com 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 complicated to migrate to that model. I'm curious how many have taken the approach of having both modes in one app. I would love to hear some experiences from having made this migration to the compat framework. On Mar 19, 2011 4:10 PM, TreKing treking...@gmail.com wrote: On Sat, Mar 19, 2011 at 12:48 PM, Chris Stewart cstewart...@gmail.com 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 experience. I'm not sure that asking them to pay for the additional work you put into a tablet version is a bad thing. It works that way on the iPad, with no issues. I think having a separate tablet version that costs more, if that's what you want to do, is fine. It's like selling a DVD and BluRay copy of a movie - same product, different platform, where one costs more because it's bigger and better. If you want both, you have to pay for both. And if user is *really* unhappy about this, you can just refund their original phone version purchase and have them keep the tablet version, so they're only paying the difference (as was mentioned earlier) for the upgrade. Do it, go. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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 doesn't give the tablet-only apps any special treatment so it will probably be drowned in other apps and doesn't take advantage of current rankings of your app. -Christer On Mar 18, 5:44 am, Zsolt Vasvari zvasv...@gmail.com wrote: 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. Option #1 is not the best, as you pointed out, you cannot force the users to pay twice. I can see forcing them to pay the difference in price if they upgrade to a tablet, but to make them buy the app all over is a huge no-no and you would end up with some very unhappy users -- and rightfully so. I think there needs to be a way to set price points based on the form factor of the device. Hopefully, the Amazon market will have this feature. On Mar 18, 12:13 pm, Chris Stewart cstewart...@gmail.com wrote: Now that I'm working on a tablet-centric version of my app, I'm considering how it will impact my existing application in the Market. As far as I can see it, there are two ways this can go: 1) Leave your existing app as-is in the Market. Build a tablet version taking full advantage of Android 3.0, setting your minSdk to 11, using your existing code base (as applicable) as a library to share core code, and sell the apps independent of each other. Here you'll need to manage two code bases, even if only the UI side which we all know varies greatly from app to app. You're also requiring users to purchase twice effectively, assuming they want the app on both their phone and the tablet-centric version on their tablet. I guess the phone version would still work on the tablet, just not optimized for it. 2) Integrate fragments into your existing application and bundle in the tablet version along with the phone version. You'll need to drop support for Android 1.5 for the compatibility library, work around API differences between the phone and tablet APIs at run-time, and handle your UI activities and views differently between platforms. I'm not sure about that last part -- but it seems like with such a different UI concept behind 3.0 with the Action Bar and the general flow of an application can be so different, that you might need to break that apart. Could be very wrong there however and would love for someone to show me otherwise. There are a few things at play here. It's the battle on the technical side of dealing with different applications (package names, projects in Eclipse, apks, etc). It's also bringing into question how you want to manage your app; whether you want to charge for a tablet-optimized version or include it with the phone app someone has already purchased. Depending on what I learn related to packaging tablet specific features to an existing phone app, I'm quite undecided on which way I'll go. I suspect many of you have already been thinking about this very subject and I'm curious how you're planning to handle it. Please do include more options as you see them. How do the different API versions impact your thinking on the subject? -- Chris Stewarthttp://chriswstewart.com- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
I TSent from my Motorola phone. Christer Nordvik cnord...@gmail.com 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 the HD version of your app. My main problem is that the Xoom doesn't give the tablet-only apps any special treatment so it will probably be drowned in other apps and doesn't take advantage of current rankings of your app. -Christer On Mar 18, 5:44 am, Zsolt Vasvari zvasv...@gmail.com wrote: 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. Option #1 is not the best, as you pointed out, you cannot force the users to pay twice. I can see forcing them to pay the difference in price if they upgrade to a tablet, but to make them buy the app all over is a huge no-no and you would end up with some very unhappy users -- and rightfully so. I think there needs to be a way to set price points based on the form factor of the device. Hopefully, the Amazon market will have this feature. On Mar 18, 12:13 pm, Chris Stewart cstewart...@gmail.com wrote: Now that I'm working on a tablet-centric version of my app, I'm considering how it will impact my existing application in the Market. As far as I can see it, there are two ways this can go: 1) Leave your existing app as-is in the Market. Build a tablet version taking full advantage of Android 3.0, setting your minSdk to 11, using your existing code base (as applicable) as a library to share core code, and sell the apps independent of each other. Here you'll need to manage two code bases, even if only the UI side which we all know varies greatly from app to app. You're also requiring users to purchase twice effectively, assuming they want the app on both their phone and the tablet-centric version on their tablet. I guess the phone version would still work on the tablet, just not optimized for it. 2) Integrate fragments into your existing application and bundle in the tablet version along with the phone version. You'll need to drop support for Android 1.5 for the compatibility library, work around API differences between the phone and tablet APIs at run-time, and handle your UI activities and views differently between platforms. I'm not sure about that last part -- but it seems like with such a different UI concept behind 3.0 with the Action Bar and the general flow of an application can be so different, that you might need to break that apart. Could be very wrong there however and would love for someone to show me otherwise. There are a few things at play here. It's the battle on the technical side of dealing with different applications (package names, projects in Eclipse, apks, etc). It's also bringing into question how you want to manage your app; whether you want to charge for a tablet-optimized version or include it with the phone app someone has already purchased. Depending on what I learn related to packaging tablet specific features to an existing phone app, I'm quite undecided on which way I'll go. I suspect many of you have already been thinking about this very subject and I'm curious how you're planning to handle it. Please do include more options as you see them. How do the different API versions impact your thinking on the subject? -- Chris Stewarthttp://chriswstewart.com- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
Sent from my Motorola phone. Christer Nordvik cnord...@gmail.com 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 the HD version of your app. My main problem is that the Xoom doesn't give the tablet-only apps any special treatment so it will probably be drowned in other apps and doesn't take advantage of current rankings of your app. -Christer On Mar 18, 5:44 am, Zsolt Vasvari zvasv...@gmail.com wrote: 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. Option #1 is not the best, as you pointed out, you cannot force the users to pay twice. I can see forcing them to pay the difference in price if they upgrade to a tablet, but to make them buy the app all over is a huge no-no and you would end up with some very unhappy users -- and rightfully so. I think there needs to be a way to set price points based on the form factor of the device. Hopefully, the Amazon market will have this feature. On Mar 18, 12:13 pm, Chris Stewart cstewart...@gmail.com wrote: Now that I'm working on a tablet-centric version of my app, I'm considering how it will impact my existing application in the Market. As far as I can see it, there are two ways this can go: 1) Leave your existing app as-is in the Market. Build a tablet version taking full advantage of Android 3.0, setting your minSdk to 11, using your existing code base (as applicable) as a library to share core code, and sell the apps independent of each other. Here you'll need to manage two code bases, even if only the UI side which we all know varies greatly from app to app. You're also requiring users to purchase twice effectively, assuming they want the app on both their phone and the tablet-centric version on their tablet. I guess the phone version would still work on the tablet, just not optimized for it. 2) Integrate fragments into your existing application and bundle in the tablet version along with the phone version. You'll need to drop support for Android 1.5 for the compatibility library, work around API differences between the phone and tablet APIs at run-time, and handle your UI activities and views differently between platforms. I'm not sure about that last part -- but it seems like with such a different UI concept behind 3.0 with the Action Bar and the general flow of an application can be so different, that you might need to break that apart. Could be very wrong there however and would love for someone to show me otherwise. There are a few things at play here. It's the battle on the technical side of dealing with different applications (package names, projects in Eclipse, apks, etc). It's also bringing into question how you want to manage your app; whether you want to charge for a tablet-optimized version or include it with the phone app someone has already purchased. Depending on what I learn related to packaging tablet specific features to an existing phone app, I'm quite undecided on which way I'll go. I suspect many of you have already been thinking about this very subject and I'm curious how you're planning to handle it. Please do include more options as you see them. How do the different API versions impact your thinking on the subject? -- Chris Stewarthttp://chriswstewart.com- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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 cnord...@gmail.com 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 the HD version of your app. My main problem is that the Xoom doesn't give the tablet-only apps any special treatment so it will probably be drowned in other apps and doesn't take advantage of current rankings of your app. -Christer On Mar 18, 5:44 am, Zsolt Vasvari zvasv...@gmail.com wrote: 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. Option #1 is not the best, as you pointed out, you cannot force the users to pay twice. I can see forcing them to pay the difference in price if they upgrade to a tablet, but to make them buy the app all over is a huge no-no and you would end up with some very unhappy users -- and rightfully so. I think there needs to be a way to set price points based on the form factor of the device. Hopefully, the Amazon market will have this feature. On Mar 18, 12:13 pm, Chris Stewart cstewart...@gmail.com wrote: Now that I'm working on a tablet-centric version of my app, I'm considering how it will impact my existing application in the Market. As far as I can see it, there are two ways this can go: 1) Leave your existing app as-is in the Market. Build a tablet version taking full advantage of Android 3.0, setting your minSdk to 11, using your existing code base (as applicable) as a library to share core code, and sell the apps independent of each other. Here you'll need to manage two code bases, even if only the UI side which we all know varies greatly from app to app. You're also requiring users to purchase twice effectively, assuming they want the app on both their phone and the tablet-centric version on their tablet. I guess the phone version would still work on the tablet, just not optimized for it. 2) Integrate fragments into your existing application and bundle in the tablet version along with the phone version. You'll need to drop support for Android 1.5 for the compatibility library, work around API differences between the phone and tablet APIs at run-time, and handle your UI activities and views differently between platforms. I'm not sure about that last part -- but it seems like with such a different UI concept behind 3.0 with the Action Bar and the general flow of an application can be so different, that you might need to break that apart. Could be very wrong there however and would love for someone to show me otherwise. There are a few things at play here. It's the battle on the technical side of dealing with different applications (package names, projects in Eclipse, apks, etc). It's also bringing into question how you want to manage your app; whether you want to charge for a tablet-optimized version or include it with the phone app someone has already purchased. Depending on what I learn related to packaging tablet specific features to an existing phone app, I'm quite undecided on which way I'll go. I suspect many of you have already been thinking about this very subject and I'm curious how you're planning to handle it. Please do include more options as you see them. How do the different API versions impact your thinking on the subject? -- Chris Stewarthttp://chriswstewart.com-Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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 that asking them to pay for the additional work you put into a tablet version is a bad thing. It works that way on the iPad, with no issues. I'm leaning more towards option #2, but I'm a little worried about managing the different views in a single application. -- Chris Stewart http://chriswstewart.com On Fri, Mar 18, 2011 at 5:10 AM, Zsolt Vasvari zvasv...@gmail.com wrote: 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 cnord...@gmail.com 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 the HD version of your app. My main problem is that the Xoom doesn't give the tablet-only apps any special treatment so it will probably be drowned in other apps and doesn't take advantage of current rankings of your app. -Christer On Mar 18, 5:44 am, Zsolt Vasvari zvasv...@gmail.com wrote: 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. Option #1 is not the best, as you pointed out, you cannot force the users to pay twice. I can see forcing them to pay the difference in price if they upgrade to a tablet, but to make them buy the app all over is a huge no-no and you would end up with some very unhappy users -- and rightfully so. I think there needs to be a way to set price points based on the form factor of the device. Hopefully, the Amazon market will have this feature. On Mar 18, 12:13 pm, Chris Stewart cstewart...@gmail.com wrote: Now that I'm working on a tablet-centric version of my app, I'm considering how it will impact my existing application in the Market. As far as I can see it, there are two ways this can go: 1) Leave your existing app as-is in the Market. Build a tablet version taking full advantage of Android 3.0, setting your minSdk to 11, using your existing code base (as applicable) as a library to share core code, and sell the apps independent of each other. Here you'll need to manage two code bases, even if only the UI side which we all know varies greatly from app to app. You're also requiring users to purchase twice effectively, assuming they want the app on both their phone and the tablet-centric version on their tablet. I guess the phone version would still work on the tablet, just not optimized for it. 2) Integrate fragments into your existing application and bundle in the tablet version along with the phone version. You'll need to drop support for Android 1.5 for the compatibility library, work around API differences between the phone and tablet APIs at run-time, and handle your UI activities and views differently between platforms. I'm not sure about that last part -- but it seems like with such a different UI concept behind 3.0 with the Action Bar and the general flow of an application can be so different, that you might need to break that apart. Could be very wrong there however and would love for someone to show me otherwise. There are a few things at play here. It's the battle on the technical side of dealing with different applications (package names, projects in Eclipse, apks, etc). It's also bringing into question how you want to manage your app; whether you want to charge for a tablet-optimized version or include it with the phone app someone has already purchased. Depending on what I learn related to packaging tablet specific features to an existing phone app, I'm quite undecided on which way I'll go. I suspect many of you have already been thinking about this very subject and I'm curious how you're planning to handle it. Please do include more options as you see them. How do the different API versions impact your thinking on the subject? -- Chris Stewarthttp://chriswstewart.com-Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to
[android-developers] Re: How is your sales model changing with the introduction of Android 3.0 and tablets, or is it?
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. Option #1 is not the best, as you pointed out, you cannot force the users to pay twice. I can see forcing them to pay the difference in price if they upgrade to a tablet, but to make them buy the app all over is a huge no-no and you would end up with some very unhappy users -- and rightfully so. I think there needs to be a way to set price points based on the form factor of the device. Hopefully, the Amazon market will have this feature. On Mar 18, 12:13 pm, Chris Stewart cstewart...@gmail.com wrote: Now that I'm working on a tablet-centric version of my app, I'm considering how it will impact my existing application in the Market. As far as I can see it, there are two ways this can go: 1) Leave your existing app as-is in the Market. Build a tablet version taking full advantage of Android 3.0, setting your minSdk to 11, using your existing code base (as applicable) as a library to share core code, and sell the apps independent of each other. Here you'll need to manage two code bases, even if only the UI side which we all know varies greatly from app to app. You're also requiring users to purchase twice effectively, assuming they want the app on both their phone and the tablet-centric version on their tablet. I guess the phone version would still work on the tablet, just not optimized for it. 2) Integrate fragments into your existing application and bundle in the tablet version along with the phone version. You'll need to drop support for Android 1.5 for the compatibility library, work around API differences between the phone and tablet APIs at run-time, and handle your UI activities and views differently between platforms. I'm not sure about that last part -- but it seems like with such a different UI concept behind 3.0 with the Action Bar and the general flow of an application can be so different, that you might need to break that apart. Could be very wrong there however and would love for someone to show me otherwise. There are a few things at play here. It's the battle on the technical side of dealing with different applications (package names, projects in Eclipse, apks, etc). It's also bringing into question how you want to manage your app; whether you want to charge for a tablet-optimized version or include it with the phone app someone has already purchased. Depending on what I learn related to packaging tablet specific features to an existing phone app, I'm quite undecided on which way I'll go. I suspect many of you have already been thinking about this very subject and I'm curious how you're planning to handle it. Please do include more options as you see them. How do the different API versions impact your thinking on the subject? -- Chris Stewarthttp://chriswstewart.com -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
