Linked by Thom Holwerda on Fri 9th Nov 2012 12:23 UTC
Permalink for comment 541639
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-07-06
I really like these interface ideas, but I have to ask, why don't we (OSNews readers) build a prototype? No, we can't build a browser that can compete with Chrome/Firefox... but we can use the web control given to us by the android UI, and that whould be good enough. (Isn't this what Dolphin does?)
The key here is that the UI would be the goal, not the end result of a browser. We would want it functional, but the fact that it is a browser should be secondary to illustrating the concept of "this is how a browser on Android should look." License it with MIT or even WTFPL. Possible even structure it so that pulling the UI into another project's prety easy. Encourage some of the alternate browsers to use it. And, if no one adopts it, well... then we can focus on getting the browser portion competitive.
I haven't done more than cursory Android development, and have too many project on my plate to jump into learning, at the moment, but surely there's some andoid developer out there with some spare time? (If not, I'll probably end up tackling it eventually.)