5 ms·

You left out the ending to that episode. Soon after Moe's becomes popular because of the 'Flaming Homer' drink, Homer tells everyone about the drink's secret i

You left out the ending to that episode. Soon after Moe's becomes popular because of the 'Flaming Homer' drink, Homer tells everyone about the drink's secret ingredient (cough syrup.) Nearly all restaurants in Springfield start serving 'Flaming Homers' and Moe's suddenly isn't the hot spot anymore. Here's hoping all the "Homers" out there leaving the App Store take their knowledge elsewhere and bring some openness to mobile development.

weego 16y ago
I'm not sure you want to be the tail trying to wag the dog if your business plan is mobile app development. Apart from an absolutely tiny fraction of the worlds population phone purchases are not driven on the apps you can buy. Out of that tiny fraction you then have to find the fraction that care about openness vs people who like to press a button and find the app just works. With the fragmentation of open OS' on phones, app purchasing is going to become chaotic and frustating. Endless choice is not condusive to a good user experience, which is why the version of *nix that everyone (in a non-developer/hacker sense) raves about from a user point of view is the "closed" one (OSX).
- probablycorey 16y ago
  The *nix part of OS X is open source http://en.wikipedia.org/wiki/Darwin_(operating_system) http://en.wikipedia.org/wiki/Darwin_(operating_system)
  - deleted 16y ago
    [deleted]
  - judofyr 16y ago
    The *nix part of OS X isn't interesting.
- alttab 16y ago
  Please stop the "fragmentation" Android argument. Its overplayed, sensationalist, and misleading when it comes to developing for android phones. With iPhone first gen, 3G, 3GS, 4G, and the iPad - theres enough screen resolution and memory differences to make the same argument.
  - davidedicillo 16y ago
    that's uncorrect. Old applications will look the same (just using 4 pixels instead of 1), text and other standard elements will be rendered at the new resolution. If you make them at 640 x 980 they will just look better, but screen-ratio is the same, so no big deal. Also a one year cycle for new products is understandable and easy to deal with. Guess what, for the next year I know exactly on which devices I will work on. For Android every other day there is a new phone, with different specs, different UI layer and a lot of other differences.
    - Tichy 16y ago
      I don't think it is an insurmountable obstacle. PCs had different screen resolutions for years, yet people still somehow managed to write web applications that looked good everywhere.
  - glhaynes 16y ago
    The argument as laid out may in fact be misleading, but the issue of fragmentation is not just screen resolution and memory differences, either. It's at least also: - display aspect ratio (far more important than resolution - worst case scenario with a "different resolution but same ratio" situation is that some things look more fuzzy than they ought to) - OLED vs LCD (colors can look substantially different) - hardware keyboard or not - hardware buttons: which ones are available and where they are placed - other hardware control availability / location / responsiveness - trackballs, non-screen touchpanels, etc - sensor availability - sensor quality: touch screen resolution and stability of tracking vary considerably - how quickly OS upgrades are made available per device / vendor / carrier and how quickly they spread across the user population - CPU speed - GPU speed and capabilities - different base applications installed with differing capabilities and UI appearance / feel Some of these of course exist in iOS world too, though not a few of the most important ones and on many of the less important, there is much less variation. One last note on iPad: few apps should have the same UI on phone-sized devices as they have on tablet-sized devices; if one is to include this as a count against iOS fragmentation, one has to also keep in mind that iOS device displays only come in 2 (radically different) physical sizes / aspect ratios whereas Android is intended to run on devices scaling from smaller screens than iPhone to larger than the iPad and everything in between. Which leads me to a question: iOS has a system-wide attribute that specifies whether the type of device is a "phone" or a "tablet"; is there a similar concept in Android?

weego 16y ago

I'm not sure you want to be the tail trying to wag the dog if your business plan is mobile app development. Apart from an absolutely tiny fraction of the worlds population phone purchases are not driven on the apps you can buy. Out of that tiny fraction you then have to find the fraction that care about openness vs people who like to press a button and find the app just works. With the fragmentation of open OS' on phones, app purchasing is going to become chaotic and frustating. Endless choice is not condusive to a good user experience, which is why the version of *nix that everyone (in a non-developer/hacker sense) raves about from a user point of view is the "closed" one (OSX).

probablycorey 16y ago
The *nix part of OS X is open source http://en.wikipedia.org/wiki/Darwin_(operating_system) http://en.wikipedia.org/wiki/Darwin_(operating_system)
- deleted 16y ago
  [deleted]
- judofyr 16y ago
  The *nix part of OS X isn't interesting.
alttab 16y ago
Please stop the "fragmentation" Android argument. Its overplayed, sensationalist, and misleading when it comes to developing for android phones. With iPhone first gen, 3G, 3GS, 4G, and the iPad - theres enough screen resolution and memory differences to make the same argument.
- davidedicillo 16y ago
  that's uncorrect. Old applications will look the same (just using 4 pixels instead of 1), text and other standard elements will be rendered at the new resolution. If you make them at 640 x 980 they will just look better, but screen-ratio is the same, so no big deal. Also a one year cycle for new products is understandable and easy to deal with. Guess what, for the next year I know exactly on which devices I will work on. For Android every other day there is a new phone, with different specs, different UI layer and a lot of other differences.
  - Tichy 16y ago
    I don't think it is an insurmountable obstacle. PCs had different screen resolutions for years, yet people still somehow managed to write web applications that looked good everywhere.
- glhaynes 16y ago
  The argument as laid out may in fact be misleading, but the issue of fragmentation is not just screen resolution and memory differences, either. It's at least also: - display aspect ratio (far more important than resolution - worst case scenario with a "different resolution but same ratio" situation is that some things look more fuzzy than they ought to) - OLED vs LCD (colors can look substantially different) - hardware keyboard or not - hardware buttons: which ones are available and where they are placed - other hardware control availability / location / responsiveness - trackballs, non-screen touchpanels, etc - sensor availability - sensor quality: touch screen resolution and stability of tracking vary considerably - how quickly OS upgrades are made available per device / vendor / carrier and how quickly they spread across the user population - CPU speed - GPU speed and capabilities - different base applications installed with differing capabilities and UI appearance / feel Some of these of course exist in iOS world too, though not a few of the most important ones and on many of the less important, there is much less variation. One last note on iPad: few apps should have the same UI on phone-sized devices as they have on tablet-sized devices; if one is to include this as a count against iOS fragmentation, one has to also keep in mind that iOS device displays only come in 2 (radically different) physical sizes / aspect ratios whereas Android is intended to run on devices scaling from smaller screens than iPhone to larger than the iPad and everything in between. Which leads me to a question: iOS has a system-wide attribute that specifies whether the type of device is a "phone" or a "tablet"; is there a similar concept in Android?