<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Exploring a Web Phone: Getting Physical</title>
	<atom:link href="http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/</link>
	<description>-- aza &#124; ɐzɐ --</description>
	<pubDate>Sun, 21 Mar 2010 11:11:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Moody Loner</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3993</link>
		<dc:creator>Moody Loner</dc:creator>
		<pubDate>Thu, 19 Feb 2009 18:41:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3993</guid>
		<description>For me personally, the "physical" design of the phone is far less important than the software running it - my ratio would be 70/30 in favour of the OS/apps over phone size, shape and weight any day(a la G1)

I like where this is going though, and I am using the G1 at the moment and it is somewhat restricted by the design (poor battery life for example) but the main thing is that; and this goes for ALL phones which interact with the web; the size of the screen and the resolution needed for a readable webpage are never going to be compatible at the sizes they[screens] are at the minute. Even mobile specific sites are poorly formatted compared to pages that laptops and even netbooks (7"+) screens can display.

Looking at the design presented, do the hard keys really need to be there? How about virtual OLED keys, they can change at will and provide more screen real estate that a hard set would take up. If, like UMAIR mentioned, you implement a plastic keyboard over the screen for tactility you would have the best of both options - why not have it flexible enough to be rolled under / over from the bottom of the screen (concealing the main part of the keyboard inside the back of the phone) to slide over the screen and back in again when the user doesn't require it. Sort of like the way a roller shutter works, except - this keeps the keyboard flat when not in use. If you look at the G1 keyboard for example, the actual height of the keys from the body is very slight - why couldn't this be implemented in a plastic overlay? You could also design the virtual icons to rotate when in landscape mode with no need to change the orientation of the keyboard.

Just a thought...</description>
		<content:encoded><![CDATA[<p>For me personally, the &#8220;physical&#8221; design of the phone is far less important than the software running it - my ratio would be 70/30 in favour of the OS/apps over phone size, shape and weight any day(a la G1)</p>
<p>I like where this is going though, and I am using the G1 at the moment and it is somewhat restricted by the design (poor battery life for example) but the main thing is that; and this goes for ALL phones which interact with the web; the size of the screen and the resolution needed for a readable webpage are never going to be compatible at the sizes they[screens] are at the minute. Even mobile specific sites are poorly formatted compared to pages that laptops and even netbooks (7&#8243;+) screens can display.</p>
<p>Looking at the design presented, do the hard keys really need to be there? How about virtual OLED keys, they can change at will and provide more screen real estate that a hard set would take up. If, like UMAIR mentioned, you implement a plastic keyboard over the screen for tactility you would have the best of both options - why not have it flexible enough to be rolled under / over from the bottom of the screen (concealing the main part of the keyboard inside the back of the phone) to slide over the screen and back in again when the user doesn&#8217;t require it. Sort of like the way a roller shutter works, except - this keeps the keyboard flat when not in use. If you look at the G1 keyboard for example, the actual height of the keys from the body is very slight - why couldn&#8217;t this be implemented in a plastic overlay? You could also design the virtual icons to rotate when in landscape mode with no need to change the orientation of the keyboard.</p>
<p>Just a thought&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Ganchev</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3955</link>
		<dc:creator>Philip Ganchev</dc:creator>
		<pubDate>Mon, 16 Feb 2009 05:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3955</guid>
		<description>I have always found it so ridiculous how uncomfortable it is to hold a phone and punch the buttons with the thumb of the same hand. The grip is very loose and the curve of the thumb is very unnatural. So I thought a lot about how to make that more comfortable. One of my designs has the buttons above the screen rather than below. This is much easier to hold. 

The obvious objection is that you have to look lower than your hand. I don't find that a problem, so I think it warrants user testing. Another objection is that the palm partly obscures the screen. To avoid that, the phone could be slightly curved to put the screen out of the way.</description>
		<content:encoded><![CDATA[<p>I have always found it so ridiculous how uncomfortable it is to hold a phone and punch the buttons with the thumb of the same hand. The grip is very loose and the curve of the thumb is very unnatural. So I thought a lot about how to make that more comfortable. One of my designs has the buttons above the screen rather than below. This is much easier to hold. </p>
<p>The obvious objection is that you have to look lower than your hand. I don&#8217;t find that a problem, so I think it warrants user testing. Another objection is that the palm partly obscures the screen. To avoid that, the phone could be slightly curved to put the screen out of the way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tobias</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3942</link>
		<dc:creator>Tobias</dc:creator>
		<pubDate>Sat, 14 Feb 2009 12:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3942</guid>
		<description>I dont want the phone to 'be' the web. I want it to be integrated into my own processes and flexible to adapt to them. Therefore I want it to be extandable on hardware and software side. For excample: It it has a camera, I want to use it to take pictures to store on the phone. But also to be able to allow the flickr webpage to use the camera. Or to connect the phone with my computer to use the phones cam as a webcam. Or the other way around if i have a better camera, nearby, tell the phone to use this one instead for the pictures...
The same excample can be told with recording audio or playing audio...

So what we need is massiv standarisation so that a all the device-creator can build uppon this standard...

ps: sorry for the bad english :)</description>
		<content:encoded><![CDATA[<p>I dont want the phone to &#8216;be&#8217; the web. I want it to be integrated into my own processes and flexible to adapt to them. Therefore I want it to be extandable on hardware and software side. For excample: It it has a camera, I want to use it to take pictures to store on the phone. But also to be able to allow the flickr webpage to use the camera. Or to connect the phone with my computer to use the phones cam as a webcam. Or the other way around if i have a better camera, nearby, tell the phone to use this one instead for the pictures&#8230;<br />
The same excample can be told with recording audio or playing audio&#8230;</p>
<p>So what we need is massiv standarisation so that a all the device-creator can build uppon this standard&#8230;</p>
<p>ps: sorry for the bad english :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: umair</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3941</link>
		<dc:creator>umair</dc:creator>
		<pubDate>Fri, 13 Feb 2009 19:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3941</guid>
		<description>balancing a full touchscreen with a physical qwerty keyboard is simple: a plastic cover that snaps onto the screen. you press the plastic button which in turn presses the screen. no electronics in the plastic keypad which allows it to be extremely thin. however, it still provides the tactile feedback that the touchscreens forego.

in the case of this change-on-the-fly prototype, the plastic buttons could be clear, so you could see through them to the screen.</description>
		<content:encoded><![CDATA[<p>balancing a full touchscreen with a physical qwerty keyboard is simple: a plastic cover that snaps onto the screen. you press the plastic button which in turn presses the screen. no electronics in the plastic keypad which allows it to be extremely thin. however, it still provides the tactile feedback that the touchscreens forego.</p>
<p>in the case of this change-on-the-fly prototype, the plastic buttons could be clear, so you could see through them to the screen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: skrat</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3933</link>
		<dc:creator>skrat</dc:creator>
		<pubDate>Thu, 12 Feb 2009 10:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3933</guid>
		<description>this is silly, what are physical buttons with icons for? we have touchscreen for icons, the only case where physical buttons are usable is QWERTY keyboard, for input.

keys with OLED display are cool, yeah, they are so cool. but not usable.

tactile feedback is nice, but not in this form/context. this is fugly</description>
		<content:encoded><![CDATA[<p>this is silly, what are physical buttons with icons for? we have touchscreen for icons, the only case where physical buttons are usable is QWERTY keyboard, for input.</p>
<p>keys with OLED display are cool, yeah, they are so cool. but not usable.</p>
<p>tactile feedback is nice, but not in this form/context. this is fugly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Hasler</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3931</link>
		<dc:creator>Sam Hasler</dc:creator>
		<pubDate>Thu, 12 Feb 2009 01:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3931</guid>
		<description>A touch screen that looks flat but feels bumpy so you can tell where your fingers are on it without looking.</description>
		<content:encoded><![CDATA[<p>A touch screen that looks flat but feels bumpy so you can tell where your fingers are on it without looking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Cardin</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3928</link>
		<dc:creator>Dan Cardin</dc:creator>
		<pubDate>Thu, 12 Feb 2009 00:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3928</guid>
		<description>I am actually quite liking the look of that phone :P. The interface is as simple as you want it. when browing the internet, or something similar you could use bookmarks, history, tabs, most used sites, etc all with only the buttons. 
It would have to be a customizeable type phone, which being called the moz phone automatically will make it so.</description>
		<content:encoded><![CDATA[<p>I am actually quite liking the look of that phone :P. The interface is as simple as you want it. when browing the internet, or something similar you could use bookmarks, history, tabs, most used sites, etc all with only the buttons.<br />
It would have to be a customizeable type phone, which being called the moz phone automatically will make it so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tylerstyle</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3927</link>
		<dc:creator>tylerstyle</dc:creator>
		<pubDate>Wed, 11 Feb 2009 22:34:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3927</guid>
		<description>No keys (only tiny power button on top), only screen, black back, almost no edges on front, fennec with gestures, running on android. Thats how!

Ahhhh, dreams...</description>
		<content:encoded><![CDATA[<p>No keys (only tiny power button on top), only screen, black back, almost no edges on front, fennec with gestures, running on android. Thats how!</p>
<p>Ahhhh, dreams&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sep332</title>
		<link>http://www.azarask.in/blog/post/exploring-a-web-phone-getting-physical/#comment-3926</link>
		<dc:creator>sep332</dc:creator>
		<pubDate>Wed, 11 Feb 2009 21:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=359#comment-3926</guid>
		<description>How about a small, thin, flexible computer encased in a sturdy plastic cover with the words "Don't Panic" inscribed on it in large, friendly letters?

http://www.bbc.co.uk/cult/hitchhikers/gallery/images/1024/babel3.html</description>
		<content:encoded><![CDATA[<p>How about a small, thin, flexible computer encased in a sturdy plastic cover with the words &#8220;Don&#8217;t Panic&#8221; inscribed on it in large, friendly letters?</p>
<p><a href="http://www.bbc.co.uk/cult/hitchhikers/gallery/images/1024/babel3.html" rel="nofollow">http://www.bbc.co.uk/cult/hitchhikers/gallery/images/1024/babel3.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
