Live data from Hacker News

IOS 6: Higher Hanging Fruit

imore.com

71–80 of 93 posts

Re: IOS 6: Higher Hanging Fruit

#72
but the features pointed out in this article have not attained widespread use, and who knows - maybe there's a reason for that. Windows phone has a negligibly small market share. WebOS died. Blackberry 10 is not even out yet. And apparently the newest Android OS is also on very few phones.http://mobile.theverge.com/2012/6/2/3058522/android-4-0-now-...

The features that iOS has allowed are in widespread use once they are implemented. This is just an observation but perhaps there's a reason Apple prefers a controlled roll out of new features.

Re: IOS 6: Higher Hanging Fruit

#73
post #55

I am amazed at how every single one idea in there is either stupid from the onset or the concept given is executed in an absolutely braindead way. Just one: direct file access. The best thing Apple did for the learning curve of computing is destroy the concept of files for the casual user. The restrictions are put on the designer who has to figure out a creative way to enable task fulfillment within those restriction…

>> "The most important enhancement is not even on the list: an iPad with several hundred apps is totally unwieldable. That should be fixed." This isn't a problem very many people face. The average iPhone user only has 65 apps installed (Source:Flurry) (I don't know about the iPad but I guess it would be around the same). Apple typically doesn't cater to the needs of a minority. With folders you should be able to get…

That would force me to spend time to manually drag everything into folders with the same cataloguing problem you face in every other domain after which I would not really be able to locate anything else.

True, the fact that I have this many apps is a professional deformation, but still the app life cycle from installing/updating, to managing/organizing, to finding and launching one is severely broken from its mental model on.

Re: IOS 6: Higher Hanging Fruit

#74

Earlier quoted context omitted.

This flies in the face of the extremely believable leaked photographs of the last week. http://www.theverge.com/2012/5/29/3049874/new-iphone-backpla...

Not to mention that that post assumes that everyone on the planet as identically sized hands.

No, the post just has to assume the AVERAGE hand size. Including smaller height people (e.g asians), and women's hands.

You really think Apple should make a larger display because an insignificant minority has larger hands?

Re: IOS 6: Higher Hanging Fruit

#75
post #73

Earlier quoted context omitted.

>> "The most important enhancement is not even on the list: an iPad with several hundred apps is totally unwieldable. That should be fixed." This isn't a problem very many people face. The average iPhone user only has 65 apps installed (Source:Flurry) (I don't know about the iPad but I guess it would be around the same). Apple typically doesn't cater to the needs of a minority. With folders you should be able to get…

That would force me to spend time to manually drag everything into folders with the same cataloguing problem you face in every other domain after which I would not really be able to locate anything else. True, the fact that I have this many apps is a professional deformation, but still the app life cycle from installing/updating, to managing/organizing, to finding and launching one is severely broken from its mental…

I agree that managing a large number of apps can be tricky. What kind of solution would you like to see? Generally I just use spotlight. One swipe, type a few letters, and the app is found.

Re: IOS 6: Higher Hanging Fruit

#76
post #3

An Exposé-style task switcher would be excellent, particularly on the iPad.

That would be nice. They could combine it with the iPad advanced gestures. Pinching your hand currently closes and app and does nothing on the home screen. How about making that zoom out to an exposé view?

Re: IOS 6: Higher Hanging Fruit

#77

There is no way that Apple is going to add any sort of direct file access into iOS 6. This would completely undermine the work that they have done to get rid of the metaphor. That said, there is certainly a problem with how files interact with iOS, mainly when it comes to email. Bridging the gap between the non-mobile file world and the pseudo-fileless iOS is going to be tricky.

Could you explain what is the matter with the filesystem metaphor?

Re: IOS 6: Higher Hanging Fruit

#78

Earlier quoted context omitted.

What's the solution to mobile file system management, then? Android has a lot going for it with its plug-and-play-esque filesystems: installed Dropbox? Now every app that uses the File API can save/load files from your Dropbox. On iOS each developer has to specifically implement each file service in each app - that's not the future.

no file system management. Or, put another way "We've invented this thing called an automobile" - "I don't get it, where do I attach my horses?"

So how do I open files made in app A in B?

Re: IOS 6: Higher Hanging Fruit

#79
post #4

Better inter-app communication a la intents on android would be great.

Yes - this is probably the one major thing that keeps me on Android. Easy sharing between apps.

It's poorly implemented on Android. I have 5 browsers installed and when in any particular app I might click a link and it will ask me which browser I want to use to open it!

Re: IOS 6: Higher Hanging Fruit

#80
post #26

My wish is that Apple adds paid upgrades for apps in the app store. I'm now close to releasing a major upgrade for an iPhone app, but these upgrades aren't going to be sustainable for me without paid upgrades (I don't want the new features to be IAP features) In the long run, this will also benefit customers because paid-upgrades will help developers add more features to the app. Users who want the new features can p…

Let's suppose you app uses an API, or whatever other thing that you do not have control over it. You make your app and release it. Then you make a paid upgrade. After some time, that thing your app rely on gets deprecated or changes. If you push an update to only people with the a paid upgrade you screw those who have not paid, leaving them with an non working app that they might have paid for. which sucks. But if yo…

Alternate strawman: you do not use paid upgrades and at some point stop making enough money to continue developing and supporting the app and the API. All of your users are screwed , too.

It's easy to envision hypothetical situations and they're all already possible, leaving customers stuck having to gauge how serious a company is and how sustainable their business model will be. Paid upgrades don't change this situation but do offer a currently blocked way for developers to make apps with a long-term plan

Post reply on HN