Linked by the_randymon on Tue 29th Jan 2013 01:23 UTC
Thread beginning with comment 551007
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[12]: Comment by Laurence
by some1 on Thu 31st Jan 2013 22:24
in reply to "RE[11]: Comment by Laurence"
I know I'm nitpicking here, but that might actually cause more work for developers as they'd have to rewrite any code that didn't expect app sizes to change mid-execution (ie at the moment you can expect screen size to be static. but now they'd have to write app so that it dynamically changes the layout while the app is running).
Very good point. Size can already change dynamically due to screen orientation change though, so may be it's possible to piggyback on that. But I'm sure there are many subtle issues the real implementation will have to deal with.
I don't think Samsung phones are the best for the money
Samsung makes a lot more than phones. And I've never said they are the best.




Member since:
2007-03-26
With the greatest of respect, you really didn't make that point clear at all.
You kept talking about Google and Android but never once mentioned any of Google's apps, so the context of your complaint seemed to be about Android itself rather than Google's apps on Android.
In all honesty, I probably wouldn't have argued with you had I realised this
I know I'm nitpicking here, but that might actually cause more work for developers as they'd have to rewrite any code that didn't expect app sizes to change mid-execution (ie at the moment you can expect screen size to be static. but now they'd have to write the app so that it dynamically changes the layout while the app is running).
Also, in the SDK itself, I'd have expected the tile size functions to be different to the screen size functions, so there might potentially be a huge can of worms in implementing such a 'minor' feature:
* apps wanting to support tiling properly would have to be compiled to support the new tile-size APIs
* those APIs will only be available in the latest SDKs
* thus apps would have to be compiled against the latest version of Android
* and thus all of the older devices running older versions of Android are now incompatible.
Obviously there's a cleaner way to go about this and I'm interested in how Samsung have worked around this issue. But now that I think about the technical complications a bit more, it may not be as simple for developers as it originally seems.
(though I'm not trying to argue that this is a reason for such features not to be implemented!)
I think that is more a matter of opinion. I don't think Samsung phones are the best for the money and while I'll agree that TouchWiz has slowly (and I mean at a snails pace) improved with time, I think it's still a massive devolution of the quality in vanilla Android.
That's just my opinion though