http://www.cnn.com/2010/TECH/mobile/08/06/try.before.you.buy.apps.mashable/index.html
didn't see this anywhere else, so.....
didn't see this anywhere else, so.....
i agree with the article that apple should offer up a return policy like android does. buy an app and you have 24 hours to return it for a full refund.
god knows, i would have like to have returned quite a few apps in my day...![]()
If you could beat a game in less than a day, I think that says a lot about the app.I disagree. If that Were the case, most kids would just buy a game, beat it, and return it. If you made the decision to buy an app before reading the reviews, I think it should be your mistake if your app was garbage. Hell, I'm sure everyone would just buy the navi app, use it, return it, and repeat the same process whenever they needed a navi system. I do think, however, there should be an extensive return process to return your app for a full refund.
I disagree. If that Were the case, most kids would just buy a game, beat it, and return it. If you made the decision to buy an app before reading the reviews, I think it should be your mistake if your app was garbage. Hell, I'm sure everyone would just buy the navi app, use it, return it, and repeat the same process whenever they needed a navi system. I do think, however, there should be an extensive return process to return your app for a full refund.
That's why a disagree with a large time limit.
I say for a game, make it 20 minutes. No one is going to beat a game in 20 minutes, especially if they've never played it before.
But I think with other things such as productivity, utilities, and photography apps, there should be an hour time limit. If you like it, your gonna buy it.
I don't know how books would work though...maybe the first chapter? lol
no....stop thinking about "time limits". make it how many times the user LOADS the app. give the user...say...3 times to load it before a confirmation prompts them.
no....stop thinking about "time limits". make it how many times the user LOADS the app. give the user...say...3 times to load it before a confirmation prompts them.
I'm sorry, I forgot that apps never crash...right? You opened it didn't you? Maybe it's a GREAT app. But it closes the first time you open it. You HAVE to exit out the second time for some reason, and the same with the third. I'm pretty sure saving it in your multitasking bar isn't considered just one use...
It wouldn't work as well as it sounds.
i agree with the article that apple should offer up a return policy like android does. buy an app and you have 24 hours to return it for a full refund.
god knows, i would have like to have returned quite a few apps in my day...![]()
no....stop thinking about "time limits". make it how many times the user LOADS the app. give the user...say...3 times to load it before a confirmation prompts them.
I like this idea.
it would work, stop trying to be a pessimist. if the app crashes that many times on you, do you want it or would you like your money back till the developer fixes it? and the developer can code in how many "loads" you get...it's not just set at 3. they can make it 10 for all we know.
They didn't really add a new feature to the app store. Just put all the Lite versions into a category.
Your example was 3 my friend, I'm basing this off of 3 load times. Btw I don't know how this makes me pessimistic, just more a realist. You get a phone call, there goes 1 load time. You get a important text message that you must reply to, there goes another load. You now have 1 left, hope your not busy.
Maybe you don't get a lot of phone calls or texts but I do. And I'd really hate to pay for an app that is based off of load times.
Like I said, it sounds great, but it wouldn't work as well as planned.
It's not even that. They don't include all the Lite versions of all apps, just 98 that they somehow handpicked. I'm sure there are far more than just 98 Lite/Free apps in the app store.
I like Angry Birds, but hasn't it gotten enough attention already? I'm hoping Apple finds a way to give some of us smaller developers more of a chance of being seen.
I'm not bitter though.![]()
![]()
i'm not a developer, but i'm sure a developer could work something into their app to recognize an actual user close verus and app closing because of a call/text/etc.