<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>bradKELLETT &#187; Mobile</title>
	<atom:link href="http://bradkellett.com/p/tag/mobile/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradkellett.com</link>
	<description></description>
	<lastBuildDate>Sun, 20 May 2012 22:28:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Brightkite Mobile Check-ins From Australia</title>
		<link>http://bradkellett.com/p/brightkite-mobile-check-ins-from-australia/</link>
		<comments>http://bradkellett.com/p/brightkite-mobile-check-ins-from-australia/#comments</comments>
		<pubDate>Tue, 29 Apr 2008 05:13:09 +0000</pubDate>
		<dc:creator>Brad Kellett</dc:creator>
				<category><![CDATA[Mobile Tech]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[australia]]></category>
		<category><![CDATA[brightkite]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[mms]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[outside]]></category>
		<category><![CDATA[SMS]]></category>
		<category><![CDATA[u.s.]]></category>
		<category><![CDATA[usa]]></category>

		<guid isPermaLink="false">http://pantsland.com/?p=272</guid>
		<description><![CDATA[I have been using the new Brightkite location-aware social network (invite-only at this point) a lot over the last few days, and one of the very common questions I hear is how I do check-ins from my mobile phone, since at this point only U.S. carriers are supported for their SMS service. The (not so) [...]]]></description>
			<content:encoded><![CDATA[<p>I have been using the new <a href="http://brightkite.com">Brightkite </a>location-aware social network (invite-only at this point) a lot over the last few days, and one of the very common questions I hear is how I do check-ins from my mobile phone, since at this point only U.S. carriers are supported for their SMS service. The (not so) secret is you can send MMS messages to email addresses with most Australian carriers (Vodafone seems to be only exception here), and Brightkite gives a personal email address for every account to send commands to.</p>
<p>Once you have an MMS compatible handset, simply:</p>
<ol>
<li>Log in to Brightkite and select <em>Account settings</em> from the left of the screen</li>
<li>Click the <em>Mobile</em> tab</li>
<li>Scroll to the bottom and find your unique account email address, program this into your phone or remember it</li>
<li>On your mobile phone, create a new MMS message</li>
<li>In the <em>To</em> field, instead of putting in a phone number, put your Brightkite email address</li>
<li>Put the standard SMS commands into the body of the message. These can be found in the Brightkite help, but the basic ones are:
<ul>
<li><em>@placemark</em> or <em>@full address</em> to check-in</li>
<li><em>!message</em> to post a message and attach it to your current location</li>
</ul>
</li>
</ol>
<p>Using this method also means you can post photos to Brightkite from your phone. To do so, just add the photo in the body of the MMS message, and the text you want to go with it in the <em>Subject</em> field.</p>
<p>Enjoy, and feel free to <a href="http://brightkite.com/people/bck">add me as a friend over on Brightkite</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://bradkellett.com/p/brightkite-mobile-check-ins-from-australia/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Review: i-mate JAQ3 In-Depth</title>
		<link>http://bradkellett.com/p/review-i-mate-jaq3-in-depth/</link>
		<comments>http://bradkellett.com/p/review-i-mate-jaq3-in-depth/#comments</comments>
		<pubDate>Wed, 08 Aug 2007 06:27:12 +0000</pubDate>
		<dc:creator>Brad Kellett</dc:creator>
				<category><![CDATA[Mobile Tech]]></category>
		<category><![CDATA[Reviews]]></category>
		<category><![CDATA[cameraphone]]></category>
		<category><![CDATA[i-mate]]></category>
		<category><![CDATA[imate]]></category>
		<category><![CDATA[jaq]]></category>
		<category><![CDATA[jaq3]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[pocket_pc]]></category>
		<category><![CDATA[poket]]></category>
		<category><![CDATA[touchscreen]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[windows_mobile]]></category>

		<guid isPermaLink="false">http://www.pantsland.com/2007/08/08/review-i-mate-jaq3-in-depth/</guid>
		<description><![CDATA[This review was originally slated to be published on MobileBurn, but scheduling difficulties meant we had to pass it over. It could be of use for some though, and it is a pretty great device, so I thought I would publish it here. Read on for all the details. Note: Click on the photos to [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.pantsland.com/wp-content/uploads/2007/08/jaq3_01.jpg" title="i-mate JAQ3"><img src="http://www.pantsland.com/wp-content/uploads/2007/08/jaq3_01.thumbnail.jpg" alt="i-mate JAQ3" align="right" /></a>This review was originally slated to be published on MobileBurn, but scheduling difficulties meant we had to pass it over. It could be of use for some though, and it is a pretty great device, so I thought I would publish it here. Read on for all the details. <strong>Note:</strong> Click on the photos to enlarge.  When I get a chance, I will add a few more live shots. <span id="more-242"></span></p>
<p>After reviewing the original i-mate JAQ back in November last year, I did not have particularly high hopes for the JAQ3. The original JAQ was i-mate&#8217;s first handset after parting ways with HTC, who designed and manufactured its handsets for some time, and was flawed in many ways. The JAQ did show promise though, and I am happy to report that virtually everything that was wrong about the JAQ has been remedied with the JAQ3. Manufactured by Chinese OEM TechFaith Wireless and sold in some markets as the UBiQUiO 501, the i-mate JAQ3 is a Windows Mobile 5.0 Pocket PC Phone Edition device, and comes packed with connectivity features and a thin, albeit wide, design.</p>
<p><strong>Physical Aspects</strong></p>
<p>Unlike most Pocket PC Phone Edition devices, the i-mate JAQ3 has a front facing QWERTY keyboard instead of a sideways slide-out design. This has plusses and minuses, as it increases one-handed usability though adds quite a bit of width to the device. This design does allow the device to come in at just 14.5mm (0.57Ã¢â‚¬Â) thick, making it the thinnest touch-screen Windows Mobile phone around currently. Length and width measure up at 126mm x 67.5mm (4.96&#8243; x 2.65&#8243;) respectively, and a weight of 160g (5.64oz) is a little on the hefty side, but not overly so.</p>
<p><!--adsense--></p>
<p>The back and sides of the i-mate JAQ3 are covered in a soft-touch rubber compound, with the front and bottom a slightly glossy hard plastic. Thankfully, it is not glossy enough to attract mass amounts of fingerprints, which is somewhat of a pet hate of mine. Decked out in black, the device looks quite classy, and will look right at home coming out of a briefcase or suit pocket. The right side of the device holds the 2.5mm headset jack, miniUSB port, and power button, with the three-way jog wheel, OK button, and camera key taking residence on the left. The 2.0 megapixel camera is the sole item on the back of the JAQ3, positioned above the easy to release yet firmly attached battery cover, itself hiding a 1250mAh battery. A covered microSD memory card slot sits atop the JAQ3, with the hard to release extendable stylus held in a silo the bottom, though it did get easier to get out over time.</p>
<p>I will make somewhat of a big proclamation now: the i-mate JAQ3 has the best QWERTY keypad I have ever used on a phone. With the exception of the space key, every key has great tactile feedback, adequate spacing that is accentuated with a convex shape, and is just about the perfect size. The only thing I can fault is that while there is only one space Ã¢â‚¬Ëœkey,&#8217; it has a pressure point at either side, which caused me to occasionally get two spaces when I hit the key plumb in the middle. Even the special characters, accessed with the Fn key, are intelligently placed. Big softkeys, call and end keys, the OK and Start button, and shortcut keys for Pocket IE and the Messaging application surround a very large 5-way directional pad. Unfortunately, the same level of quality found on the keyboard isn&#8217;t shared with the jog wheel, which has a terrible feel when pressed to select items. I also wish the keyboard backlight stayed on a little longer, or better yet, had a setting to control the time it stayed on.</p>
<p>The i-mate JAQ3 has a bright, relatively clear QVGA resolution touch screen, though its landscape 2.4Ã¢â‚¬Â screen is smaller than most other Pocket PC phones. This is further perceptible due to the handset&#8217;s size. Other than the size, there is not a lot to complain about, with the screen accurately detecting taps with the stylus, and having adequate readability even in bright sunlight.</p>
]]></content:encoded>
			<wfw:commentRss>http://bradkellett.com/p/review-i-mate-jaq3-in-depth/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Nokia N73 Review</title>
		<link>http://bradkellett.com/p/nokia-n73-review/</link>
		<comments>http://bradkellett.com/p/nokia-n73-review/#comments</comments>
		<pubDate>Mon, 25 Sep 2006 11:10:50 +0000</pubDate>
		<dc:creator>Brad Kellett</dc:creator>
				<category><![CDATA[Mobile Tech]]></category>
		<category><![CDATA[Reviews]]></category>
		<category><![CDATA[auto_focus]]></category>
		<category><![CDATA[carl_zeiss]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[n73]]></category>
		<category><![CDATA[Nokia]]></category>
		<category><![CDATA[qvga]]></category>

		<guid isPermaLink="false">http://www.pantsland.com/2006/09/25/nokia-n73-review/</guid>
		<description><![CDATA[The Nokia N73 has been a bit of a roller coaster for me. When it was originally announced and I wrote the story for MobileBurn, I didn&#8217;t like it. It just looked funny to me, and I wasn&#8217;t really interested. Here we are though, five months later, the N73 has been released and I have [...]]]></description>
			<content:encoded><![CDATA[<p><a class="tt-flickr" href="http://www.pantsland.com/album/photo/252153279/Nokia_N73.html"><img width="240" height="152" border="0" style="float: right" alt="Nokia N73" src="http://static.flickr.com/113/252153279_d7a378bad9_m.jpg" /></a> The Nokia N73 has been a bit of a roller coaster for me. When it was originally announced and I wrote the story for MobileBurn, I didn&#8217;t like it. It just looked funny to me, and I wasn&#8217;t really interested. Here we are though, five months later, the N73 has been released and I have one in my hand &#8211; and I love it. Read on for my initial impressions/mini review of this powerful multimedia handset.</p>
<p><span id="more-180"></span><!--adsense--></p>
<p>To start with, the Nokia N73, despite its top-heavy look, feels great in the hand. It is well weighted, and its size makes it easy to get a firm grasp on. It is on the large end of the size scale, but is not so big as to prove awkward &#8211; and considering its features, it is not an unreasonable size at all.</p>
<p><a class="tt-flickr" href="http://www.pantsland.com/album/photo/252153319/Nokia_N73.html"><img width="240" height="104" border="0" alt="Nokia N73" style="float: left" src="http://static.flickr.com/86/252153319_e6720f9871_m.jpg" /></a> The first thing you will notice about the Nokia N73 is its large, high resolution (QVGA, 240&#215;320 pixels) screen. This has to be one of the N73&#8242;s star features; it is bright, clear, and the only thing that I would say can match it is the N73&#8242;s Nseries cousin, the N80. With that said, the N73&#8242;s screen is still larger, and in my opinion, better to use.</p>
<p><a class="tt-flickr" href="http://www.pantsland.com/album/photo/252153216/Nokia_N73.html"><img width="146" height="240" border="0" alt="Nokia N73" style="float: right" src="http://static.flickr.com/106/252153216_3788b56668_m.jpg" /></a>Arguably second to the screen, the N73&#8242;s other draw card will be its camera. The camera looks great on paper: a 3.2 megapixel resolution and Carl Zeiss auto-focus lens put it on the same level as the video-centric N93, as well as the N73&#8242;s rival, the Sony Ericsson K800. I can&#8217;t comment too much on the camera due to lack of testing, but expect some sample photos and notes to be posted here in the next couple of days. What I will say though, it is seems the camera application has a little trouble when it comes to the preview before taking a shot. The viewfinder gives everything a bad blue tinge, which then disappears after taking the shot. The offshoot of this is the fact that it is hard to toy with white balance pre-photo, but at least the tinge doesn&#8217;t come out in the final image.</p>
<p>The keypad featured in the Nokia N73 will be its weakness for a lot of people. While I don&#8217;t have a problem with it personally, the numerical keypad is rather small. To offset this, the keys have a good sized ridge on them, and provide a great level of tactile feedback. On the positive side, the N73&#8242;s joystick is one of the best I&#8217;ve ever used. It is firm, and really feels like it will last the distance, unlike many other phone joysticks that feel like they will break after a period of use.</p>
<p><a class="tt-flickr" href="http://www.pantsland.com/album/photo/252153307/Nokia_N73.html"><img width="240" height="165" border="0" alt="Nokia N73" style="float: left" src="http://static.flickr.com/113/252153307_be09b4d31b_m.jpg" /></a>One, albeit small, thing that I&#8217;m happy to see has returned to a handset is the small blue indicator light on the front of the device. This light blinks periodically after the display has gone to sleep to show that the handset is turned on, saving you from activating the screen. The only pick I can make on this light is that I would prefer that it either changed color, or blinked in a different fashion when you have a missed call or new message.</p>
<p>On the software side of things, it is all standard Nokia S60 smartphone fare. The Quickoffice suite is pre-installed, allowing you to view and edit Microsoft Word, Excel, and PowerPoint files. The Adobe Reader application is also here, as are the usual fair of PIM applications, plus Nokia&#8217;s Lifeblog software. The speed of the S60 v3 UI is greatly improved over v2, and the N73 is one of the faster S60 devices I have used of late. The handset includes a &#8217;3D Ringtone&#8217; application, which utilizes the handset&#8217;s stereo speakers to make 3D effects, such as ZigZag and Circular, when you receive a call. These speakers also have the effect of making ringtones extremely, almost ear piercingly, loud when you use an MP3 as a tone.</p>
<p><a class="tt-flickr" href="http://www.pantsland.com/album/photo/252153245/Nokia_N73.html"><img width="240" height="137" border="0" alt="Nokia N73" style="float: right" src="http://static.flickr.com/91/252153245_0706acb753_m.jpg" /></a>One thing that I have noticed, which could possibly be remedied with a firmware update, is occasionally the signal meter will fluctuate from full to almost nothing several times, even with the phone completely stationary. Curious indeed.</p>
<p>Overall, the Nokia N73 marks one of the best, if not the best, S60 smartphone I have ever used. Good speed, a great camera, and great design make it a must have in my opinion. If you are looking for a solid smartphone with an awesome screen, I can honestly recommend the Nokia N73.</p>
]]></content:encoded>
			<wfw:commentRss>http://bradkellett.com/p/nokia-n73-review/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Marketing Mobile Handsets</title>
		<link>http://bradkellett.com/p/marketing-mobile-handsets/</link>
		<comments>http://bradkellett.com/p/marketing-mobile-handsets/#comments</comments>
		<pubDate>Fri, 08 Sep 2006 12:56:52 +0000</pubDate>
		<dc:creator>Brad Kellett</dc:creator>
				<category><![CDATA[Commentary]]></category>
		<category><![CDATA[Mobile Tech]]></category>
		<category><![CDATA[auto-industry]]></category>
		<category><![CDATA[handset-manufacturers]]></category>
		<category><![CDATA[Handsets]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Motorola]]></category>
		<category><![CDATA[Nokia]]></category>
		<category><![CDATA[Samsung]]></category>
		<category><![CDATA[Word-of-Mouth]]></category>

		<guid isPermaLink="false">http://www.pantsland.com/2006/09/08/marketing-mobile-handsets/</guid>
		<description><![CDATA[One of the hardest parts of my job is remembering model numbers of handsets. For a long time, confusing numbering has been the norm, but finally some of the marketing folk that work with handset manufacturers are waking up to the fact that model names, rather than numbers, are the way to go. Samsung are [...]]]></description>
			<content:encoded><![CDATA[<p>One of the hardest parts of my job is remembering model numbers of handsets. For a long time, confusing numbering has been the norm, but finally some of the marketing folk that work with handset manufacturers are waking up to the fact that model names, rather than numbers, are the way to go. Samsung are by far the worst when it comes to naming schemes, followed by Nokia, but the later has <a title="Read the news a Yahoo! News" href="http://news.yahoo.com/s/nm/20060907/tc_nm/nokia_phones_dc">recently announced</a> (in a very informal way) that it will be moving to a meaningful naming scheme.</p>
<p><!--adsense--></p>
<p><a title="Read the post at MobileScraper" href="http://www.mobilescraper.com/article/537/Nokia-Decides-that-Giving-Phones-Stupid-Names-a-Great-Idea.html">Unlike Barry Allwood at MobileScraper</a> (like the name), I think this is a great idea &#8211; with a caveat. Like Barry, I hate Motorola&#8217;s confusing naming. Why are vowels so bad, Motorola? What I do like, however, are names like LG&#8217;s Chocolate. Think about the auto industry, manufacturers do not name their vehicles with long, confusing numbers, but instead give them names that are memorable, which increases model awareness and encourages word of mouth marketing.</p>
<p>I don&#8217;t think a pure name based system is the answer, though; Too many names will get just as confusing as the numbers. What I would love to see is manufacturers using names for ranges of products, which are then broken down with short, easy to remember numbers. Samsung, which I previously called the worst offender, has actually begun introducing this method (though only on a very small range of handsets currently). Samsung has its &#8216;Ultra&#8217; range, which is then broken down into numbers based on the thickness of the handset (Ultra 9.9, Ultra 6.9), and while I don&#8217;t particularly like the decimal point in there, I think this is the way of the future.</p>
<p>Imagine it, the Ford SMAD-1901 &#8211; pretty memorable&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://bradkellett.com/p/marketing-mobile-handsets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Click Wheel &#8211; Not the Solution for Phones</title>
		<link>http://bradkellett.com/p/click-wheel-not-the-solution-for-phones/</link>
		<comments>http://bradkellett.com/p/click-wheel-not-the-solution-for-phones/#comments</comments>
		<pubDate>Sat, 19 Aug 2006 01:49:38 +0000</pubDate>
		<dc:creator>Brad Kellett</dc:creator>
				<category><![CDATA[Mobile Tech]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Convergence]]></category>
		<category><![CDATA[iPod]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Music]]></category>
		<category><![CDATA[Nokia]]></category>
		<category><![CDATA[Phone]]></category>
		<category><![CDATA[Samsung]]></category>

		<guid isPermaLink="false">http://www.pantsland.com/2006/08/19/click-wheel-not-the-solution-for-phones/</guid>
		<description><![CDATA[To begin, I&#8217;m not one to bad mouth convergence. While I have no real use for a music phone, I certainly don&#8217;t have a problem with manufacturers combining an audio player and a phone &#8211; it does seem like a good match. What I do have a problem with, is the fact that many are [...]]]></description>
			<content:encoded><![CDATA[<p><img width="150" height="115" style="border: thin solid ; float: right" src="http://www.pantsland.com/wp-content/uploads/2006/08/WindowsLiveWriter/ClickWheelNottheSolutionforPhones_A641/i300_launch_thumb%5B1%5D1.jpg" /> To begin, I&#8217;m not one to bad mouth convergence. While I have no real use for a music phone, I certainly don&#8217;t have a problem with manufacturers combining an audio player and a phone &#8211; it does seem like a good match. What I do have a problem with, is the fact that many are trying to take the interface of one very popular music player and make it work on a mobile handset.</p>
<p>Of course, the device I&#8217;m referring to is the iPod, and the interface is the click (or scroll) wheel. This input device is great in the audio player space, but it was not designed as, and will never work as, an input device for a phone.</p>
<p>Two recent handsets that come to mind are the Samsung i300/i310 and the LG KV2400. Both are respectable devices in their own right, especially with Samsung&#8217;s 4GB/8GB hard drives, yet both spoil functionality by using a click wheel.</p>
<p>One of the biggest problems with adding a click wheel to a phone is the space constraints. While the iPod&#8217;s wheel is very easy to use, when you reduce its size and place it with a myriad of other buttons, usability is severally compromised. Nokia, for once, have actually taken the right step on this issue &#8211; their N91 music phone still uses traditional phone navigation, and modifies the music player to accommodate this &#8211; the addition of non-click wheel music control keys is the icing on the cake.</p>
<p>I do hope that the trend I&#8217;m seeing of adding a click wheel to a phone does not continue, and that manufacturers wake up to the face that the usability of the handset should not be compromised to add a &#8216;cool factor&#8217; to the music side of things.</p>
]]></content:encoded>
			<wfw:commentRss>http://bradkellett.com/p/click-wheel-not-the-solution-for-phones/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

