Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Misleading summary (Score 1) 518

The central theme of the article is whether or not tech companies should continue try to grow their business, or should they decide to not compete with established industries. A specific cited example is that Apple created a net job loss through iTunes by ruining Tower Records. The summary makes it sound like the article is asking whether or not tech companies should feel bad for the fact people play Farmville rather than look for a job.

Comment Re:A question about Android (Score 3, Informative) 161

The UI changes to the homescreen would be bad on a screen smaller than 7". Multiple windows, side menus, physical buttons replaced by software buttons, size of buttons relative to the screen, this sort of thing. Essentially with the bigger screen, screen space can be taken up by secondary needs (launcher, menus, options, etc), whereas on the small screen, 95% of the screen is dedicated to the user's immediate content, and things are relatively big to improve the user experience. In Honeycomb, UI elements are smaller, and screen area can be dedicated to not just a primary task, but useful information and quick access to facets of the program formerly hidden behind the menu button.

Comment Re:Fragmentation (Score 2) 193

From Android Development's Website:

Android 3.0 brings a new UI designed for tablets and other larger screen devices, but it also is fully compatible with applications developed for earlier versions of the platform, or for smaller screen sizes. Existing applications can seamlessly participate in the new holographic UI theme without code changes, by adding a single attribute in their manifest files. The platform emulates the Menu key, which is replaced by the overflow menu in the Action Bar in the new UI. Developers wanting to take fuller advantage of larger screen sizes can also create dedicated layouts and assets for larger screens and add them to their existing applications.

So, to sum up, old apps work fine, a small tweak will make the UI look right, and you can add a custom tablet UI to existing software.

Comment Re:Fragmentation (Score 1) 193

Supposedly there is a 2.4 Ice Cream as the next smartphone iteration of Android. I'm not sure what the numbers mean exactly. I think this fragmentation might be good because you want apps that are written explicitly for tablets, and take advantage of the screen size, that don't have to work on small screens. Also, 2.x apps are going to be able to run on Honeycomb according to Google. From what I've seen of the Honeycomb SDK, the changes are to interact with the new UI, the hardware API's seem unchanged.

Comment What my driving instructor said (Score 1) 220

Back when I was doing driver's ed, my instructor asked me if I played video games. He said that he had noticed that people who played video games tend to grasp the visual feedback quicker than most people. So that most 15 year olds see a straight road and don't steer, gamers would constantly make corrections based on visual feedback, because that was already a natural thing to do.

Slashdot Top Deals

Asynchronous inputs are at the root of our race problems. -- D. Winker and F. Prosser