Flipboard for Android debuting on Galaxy SIII

[Anibal P]

Exclusive to the Galaxy SIII? WTF? Android really doesn't need forced fragmentation due to business deals like this on top of the fragmentation issues that already exist :(

The day the GS3 hits the public the APK for Flipboard will go out to the public too, the beauty of Android, we can get around pesky things like exclusivity fairly quickly, even if it has any code to try and keep it on the GS3, it will be bypassed fairly quick.

[Boz]

Density independent pixels and scalable graphics and all that are great, if you don't care about your app looking like **** and conforming to different size devices.

For a good app it needs to be specifically designed for the device, for high res devices you need the proper size images for the proper size "buttons", then some of those devices with the same res can be up to 2 inches different in size, so one of them would have fewer and bigger but higher density thumbs which needs to be coded, but can to some degree be done with intelligent scaling algorithms.

Tis same problem recurs with every different resolution and screen size. Resolutions reasonably close can be fit into the same GUI, just be using flow and filling in white space and padding. But you gave to take physical screen size into account separately. A 3.5 inch device and a 4.5 inch device with the same res can't use the same layout, either one would have to big buttons or the other to small, or one would have to much padding while the other the icons would be on top of each other, one would have shap graphics, the other blurry.

Vectors would fix some of these problems, but they wouldn't work for flipboard and it's graphics anyway. And would just fix the blurriest, not the size and screen size and layout issues.

Nothing you said here makes any sense because "problems" you describe don't exist. You cab include graphics and visuals depending on what type of pixel density the display is and provide assets for that specific density.

ADT is pretty well thought out and provides great environment in development. Android devices are split into 3 categories: high density, medium density and low density and you can include assets for you specific designs and UI based on those 3 categories if you choose so. This is not by any means a must. You can always include assets and UI elements for higher density devices and they will scale down to other vsrsions the same way it works on iOS.

You don't have to code anything in that regard.

Stick to opinions because trying to argue something that you just off-handedly read somewhere online makes you look silly.

[Hell-In-A-Handbasket]

The day the GS3 hits the public the APK for Flipboard will go out to the public too, the beauty of Android, we can get around pesky things like exclusivity fairly quickly, even if it has any code to try and keep it on the GS3, it will be bypassed fairly quick.

Agreed, friend ran some program and changed the ID of his phone so he could put Netflix on it when Netflix first came out. I though that was Awsome.

[HawkMan]

Nothing you said here makes any sense because "problems" you describe don't exist. You cab include graphics and visuals depending on what type of pixel density the display is and provide assets for that specific density.

Yes you can, but that's still a lot more work. And doesn't solve the different sizes problem.

Either way, your argument is that developing for 20 different resolutions, and 20 different screen sizes and at least 3 different screen size ratios isn't more work. But your argument still include a lot more work. Just less work than if google hadn't made a good dev tool. It's still a lot more work, just not as much as it would have been.

Writing self contradicting argument only makes you look silly.

[Boz]

Yes you can, but that's still a lot more work. And doesn't solve the different sizes problem.

Either way, your argument is that developing for 20 different resolutions, and 20 different screen sizes and at least 3 different screen size ratios isn't more work. But your argument still include a lot more work. Just less work than if google hadn't made a good dev tool. It's still a lot more work, just not as much as it would have been.

Writing self contradicting argument only makes you look silly.

I'm not contradicting myself. You are jumping from one topic to another. I said, the reason they have more work and delay is because they designed the app for a single resolution and thus now have more work to do it properly on Android that supports multiple resolutions on various devices.

When you design and develop for Android initially it's not more work because you setup and design your app to the way you should on Android to accomodate different resolutions. You don't develop app for 3 different densities and code that way. That would be silly and usually happens when people developed something for a fixed resolution and are now trying to convert it to Android's way.

Different resolutions are not fragmentation. That's like saying, Windows and OSX development is fragmented because different Macs running OSX run with different resolutions. It's absurd.

[alphaomegainfinity]

I just hope it eventually becomes available to the poor ol' Galaxy S :) .

[Hell-In-A-Handbasket]

Here is the APK Don't know which devices it will work for, hopefully all

http://forum.xda-developers.com/showthread.php?t=1644212

[Boz]

Working great on my Galaxy Nexus

[LittleNeutrino Veteran]

So far the app is rather nice even though for the most part the only difference it has from Currants is the facebook/twitter integration.

[Boz]

So far the app is rather nice even though for the most part the only difference it has from Currants is the facebook/twitter integration.

The biggest problem with Flipboard and why I stopped using it is that there is no easy way to see all news and updates from feeds as a list.. you have to flip individually through each story which is really awful from usability standpoint. In Currents you can flip through them individually but you can also see a list of all items in a feed as a list and quickly glance over what you are might be interested in. Huge plus from me on that for Google.

[Dick Montage]

Very pretty interface, but it seems like a very slow way to access stories?

[AbandonedTrolley]

Very pretty interface, but it seems like a very slow way to access stories?

Yeah technically it's nice and pretty, in terms of functionality it's a bit long winded,