4 ms·
The OP raises some valid points (agree with them or not). > 1. Phone storage vs. SD card storage As much as people much like expandable storage it is, by defi
by cletus 16y ago
The OP raises some valid points (agree with them or not).
> 1. Phone storage vs. SD card storage
As much as people much like expandable storage it is, by definition, more complicated. There are currently two simple models:
1. All internal (the Apple model); and
2. All external (the digital camera model, even though some do have up to 1-2GB of internal storage).
Having a mix is like having two hard drives. You're suddenly asking your users to make decisions about things they probably don't care about or that they do care about in ways you can't predict. Will they want this app on internal or external storage? What about this music?
All external works for digital cameras because the OS (firmware, etc) is in the camera. The photos and videos go on the card. You don't lose functionality when you take out the card (apart from edge cases like saving profiles on certain high end DSLRs).
This is why I believe iDevices will never have an SD card slot. Or, if they do, it will only be for very limited use, much like the Camera Connection Kit on the iPad.
> 2. The epic list of applications (ELOP)
I find this a little strange too. If someone installs something, it appears at the top level in iOS. On Android, mainly due to manufacturer customization, you have less "home pages" for your apps (and they're generally filled with crud you need to remove). Making your newly downloaded app harder to find is a little odd.
> 4. Inconsistent interaction
This is like the one/two button mouse argument. iDevices have one button, the home button (as well as volume and, on the iPad, a mute/orientation lock switch). In part for this reason, iOS apps are extremely consistent.
Android has 4 buttons: back, home, menu, search. IMHO at least 2 of them are unnecessary. App developers use them in completely inconsistent ways, which tends to frustrate the user.
The way I describe iOS (and Apple in general) is that they make the right choices for most users most of the time. Nothing will ever make everyone happy. The uncomfortable truth is that this is really the best thing to do for the market as a whole.
Many tech-savvy people chafe against what they see as choices being taken away from them (which they are) but they're also under the illusion that a) they need these choices and b) having these choices, by definition, is better. Neither is true. You may like these extra choices but that doesn't mean that they're good or that you need them.
Again, we can make a Windows/Mac comparison. Windows apps are horribly inconsistent. Mac apps are almost completely consistent. That makes learning new Mac apps much, much faster for experienced Mac users. By the same token, put a Mac user in front of Windows or a Windows user in front of a Mac and both will flounder (I don't buy the argument that Macs are inherently easier; it still comes down to what you're used to). The learning curve is definitely gentler on Macs however. Same for iOS (vs Android).
- cryptoz 16y agojust a nit to pick: > Android has 4 buttons Android does not define the number of buttons. My Android phone has three buttons. The Motorola Xoom tablet running Honeycomb (Android 3.0) has 0 of those buttons. It has only power and volume, I believe.
- cletus 16y agoAnd how is that not a worse problem?
- ffumarola 16y agoDepends what you expect. Copied from below: I like that different phone manufacturers have slightly different concepts of what makes the OS the most functional. Because at the end of the day each iteration will better future phone models as they learn what the market likes more. Instead of what one companies design team likes better.
- cryptoz 16y agoFlexibility in an OS to handle a variety of hardware is not a problem at all. In fact, it's a very good thing. Google is letting manufacturers with experience decide the best way to add buttons - or not add buttons - to their devices. Android devices without physical buttons will likely have software equivalents. To most customers, there isn't much difference between a hard and a soft button.
- nuclear_eclipse 16y ago> Having a mix is like having two hard drives. You're suddenly asking your users to make decisions about things they probably don't care about or that they do care about in ways you can't predict. Will they want this app on internal or external storage? What about this music? Except it's not. Android doesn't give the user any options, with one exception that almost nobody ever needs to worry about. See my comment at http://news.ycombinator.com/item?id=2327424 http://news.ycombinator.com/item?id=2327424 >> 2. The epic list of applications (ELOP) >I find this a little strange too. If someone installs something, it appears at the top level in iOS. On Android, mainly due to manufacturer customization, you have less "home pages" for your apps (and they're generally filled with crud you need to remove). Making your newly downloaded app harder to find is a little odd. This boggles my mind. What is so hard about pressing a button on home screen and then finding the application in a sorted list of icons? If it's something you'll be using often, you can put it directly on a homescreen, but otherwise, how is it hard to find? Just because it's different from iOS doesn't mean it's hard; it just isn't what you're used to. Edit: Further on this note, iOS allows you to group app icons into subfolders on your home screen. How is that any easier than having a single sorted list for finding everything installed on your phone, other than the fact that you were the one to define those folders? How is that any different than being the one to define what's on your home screens?