Subscribe to RSS
Posts Tagged ‘mobile’
Lessons for eComm “Lightning Talk” speakers
Earlier this year at eComm 2009, I gave my “lightning talk”. At the end of the day, I have to accept that I did a terrible job. An eComm “Lightning Talk” is a 5-minute presentation. My problem was, I really just condensed a 15 minute talk down to five minutes. While I did cut out a lot from the larger talk, I didn’t focus the presentation enough. I practiced and practiced the talk and successfully completed the presentation in five-minutes, but it tried to present too much information across too many directions.
If I give another such lightning talk, I will focus the entire thing down to one main point. In the above talk, I waste too much time on the “how” (the implementation) without enough focus on the “what” (the result). This is of course because I’m a geek and I find the “how” really interesting. But what is significant about the research I was presenting here is really the “what” – and I failed miserably in getting that point across. In fact, what this research was about was very much in tune with what Lee Dryburgh likes to call intention-based economics:
What we care about with intention based economics is human psychology and behaviour, both individual and in aggregate. … what we need to build for is access to ever more personal information, i.e. about the human behind the endpoint. Privacy does not exist looking long-term. Ever more personal information is the new currency, which underlies intention-based economics, and people will increasingly trade it for free access to services.
… telecom networks receive vastly more human attention coming in from the edges and transit much more “intention data” than Google, in the form of telecom signaling. But it’s latent, not acted upon and thrown away. They actually throw away their most precious asset and plan to continue charging for their long-term least worthy asset (voice transmission).
This research looked at “intention data”. Instead of throwing away this telecom signaling information, as the telecom companies currently do, this research used the data to study actions of the “human behind the endpoint” to include historical analysis as well as making predictions, i.e. determining intent.
The signaling data of who is talking to who, combined with their locations, recent movements, and so on, can be used to predict future actions (intent). For example, a certain flurry of a certain kind of activity might suggest that a group of friends are probably going to go see a movie together. Advertisers would be interested in such fore-knowledge, one would think.
I think it’s particularly interesting that we were able to do this in the real world, using real phones available today, and doing so without the user’s active involvement and without the permission or participation of the carrier, i.e. as an independent third-party with no special relationship to the carrier. We did it by supplying users with modified edge-devices (phones) that provided “ambient awareness” streams. These phones didn’t require GPS – we used cell tower and bluetooth proximity for location data. We didn’t need a very large sample to get meaningful results. Everything we did in this research could be done by the carriers and of course they may be doing it already and we wouldn’t know. This research shows how practical intention-based economics is and that it may not be as far off or as abstract as we think.
This research basically turned humans into “sensors” emitting data about their location and, more importantly, who they are talking to (and texting with), all as a surreptitious side-effect of carrying around a mobile phone and performing their every day routines. In general, besides location, other behaviors are very powerful indicators (behaviors like “what are they taking pictures of?”). A single data point may not provide much insight, but when viewed over time, and in relation to other human actions and behaviors, it becomes incredibly powerful. With this power comes responsibility. As Lee says “Privacy does not exist looking long-term.” This research doesn’t attempt to answer that question. Rather, it explicitly intends to raise awareness that it must be addressed and, given the results we were able to obtain in this research in fairly short time and with relatively modest resources, it needs to be considered sooner rather than later.
<GRATUITOUS PLUG>
We did this research as contract work – if you’d like to learn more or perform similar research contact us here: sales@telEvolution.com
</GRATUITOUS PLUG>
Update on my eComm presentation
This has not made it to the eComm site yet, but here’s what my 5-minute lightning talk will be about:
Mobile phones are practically ubiquitous. Everyone carries them and most of them are turned on and connected 24×7. Today’s mobile phones, even the least expensive ones, have sensors, spare cycles, and connectivity. These resources can be applied to a wide variety of Social Telemetry Applications, to powerful, and potentially even troubling, effect. We present findings of a real-world deployment of such a system.
And here’s a sneak-peak of the talk:
eComm presentation Wednesday, March 4, 4:55PM Salon E
I look forward to seeing you there.
Nokia N97 – when will they get that it’s not just about a touchscreen?
Om has a nice post about the forthcoming Nokia N97 Superphone to be released “sometime in the second quarter of 2009.” He says:
As for the 5800 Xpress, a friend of mine recently brought one to the U.S. and after I played around with it for an hour, my response was meh! The touch was OK, just like it’s OK on any other device, but it’s not as responsive as the iPhone. So no, it’s not an iPhone killer, not by any means.
The N97 however, seems, like a worthy competitor… it will be sold in the U.S., where it’s going to cost $650; it will go on sale in June 2009…
I agree with these comments, but I would add that none of these other mobile players, whether carriers or phone manufacturers, seem to understand what battle they are fighting. They seem to think it’s about touch screens and hardware. Even Om emphasizes the touch screen issue:
The very fact that Nokia is only now getting out touchscreen phones shows that as a company it is stuck in bureaucratic quicksand, with a culture of consensus that makes it difficult to respond to new challenges. Nokia — and I have been following them for a while — has become one of those companies that, much like Microsoft, is good with announcements, not so great with the follow-up.
Stuck in a “bureaucratic quicksand” perhaps, but it’s really more than that. Nokia is selling just another piece of hardware. At one time, that mattered, because that’s how the industry worked. Apple changed all that and nobody has really grasped the magnitude of it yet. Apple changed everything about the mobile landscape. It may seem the same, but it’s not. It seems few people really appreciate what happened. That’s good for Apple – bad for the all their competitors. As long as Apple’s would-be competitors continue to respond in 20th century ways to the new 21st century mobile phone landscape, Apple will continue to run roughshod over the industry.
Nokia is offering a Do-it-yourself solution, where users have to bring their own carrier, service plan and applications. That’s never going to be an “iPhone killer” because it’s not the same market – it’s not the same battle at all.
The problems for Nokia and any would-be “iPhone killer” don’t end with simply realizing the situation they’re in. Once they realize it, they will also realize they can’t compete on the same playing field. Apple owns the hardware, the distribution, and the service plan. (I know people get an AT&T plan with iPhone, but it might as well not be. It is an iPhone plan.) Nokia can’t do this. They don’t have distribution or control over the service plans. The carriers can’t do this. They don’t have Apple’s expertise at controlling the hardware. And most importantly, none of them have the App Store.
It’s not about the hardware. If it were, Apple would already be in trouble. Compared to many other mobile phones, including many of those from Nokia, the iPhone is a piece of junk, hardware-wise. Apple isn’t winning because their phones are better. Apple is winning because the experience is better. People can actually use the iPhone. Ordinary non-technical people are doing things they have never done before on a mobile phone – things they would never do on a Nokia or other DIY solution.
Nokia may do fine in the DIY niche they’re in – but they will never have anything approaching an “iPhone killer” unless they make a bunch of acquisitions and change who there are.
Why iPhone is not “boring”
I’ve seen several comments and posts recently suggesting that iPhone is just another boring story.
I believe an historic day passed us by last week. Sure, Apple opening up the iPhone App Store received some press, but I haven’t yet read anything that really “gets” the significance of this event. There’s all kinds of moaning and groaning about the quality of apps, the price etc. and while there may be truth to these gripes, the fact most people are missing is that, unless Apple screws it up in some big way, the world changed last week.
I consider it as potentially significant as the effect the introduction of WWW and Mosaic had on the Internet. Last week, Apple changed everything about the mobile phone ecosystem and I don’t think very many people noticed – yet. That world will never be the same, just like the Internet was never the same after HTTP.
The other players, whether device makers or carriers, are not even on the same planet – it seems like they aren’t even aware of the situation. They aren’t even asking the right question, to say nothing of having the right answer. There are hundreds of millions of mobile phones with Java on them – and nobody knows it. Most people have no idea how to buy anything for their phone beyond ringtones (if they even know how to do that). Their phones probably have the capability to run apps – but there is no place to get them. Well, or say in the case of Symbian phones, there are too many places to get them.
Apple is changing all that with the iPhone store. And gripe all you want about the warts of the current apps or the prices or whatever, all that mises the point. Ordinary people now know how to obtain apps (free or otherwise), how to install them – perhaps more significantly, the entire idea of adding apps to a phone is now “normal” – it’s now part of the collective consciousness.
And developers have a place to put them, not “yet another place”, but the place, the one and only place. I always said iPhone was about iTunes from the start.
Of course this is about distribution and execution – Apple has the right capabilities to create this “perfect storm”. Unlike carriers, Apple knows how to build and manage software and services (can you say iTunes?). Unlike other device makers, Apple has their own distribution and marketing – they don’t need to rely on the carriers to market their device.
The future of Mobile is now Apple’s to lose and the rest of the mobile space better be worried.
iPhone SDK, not quite
I have not had time yet to figure out whether Apple’s direction with the iPhone SDK is a good or bad thing. Apple will be taking the approach that they will be the only way to distribute apps, the gatekeeper. That sounds bad, but I’m told by people I trust that the process will be reasonable, better than the situation we have for distribution of freeware with Symbian Signed for Nokia phones.
The SDK is available now, in beta, but not for writing apps that actually run on the phone, if I understand correctly, but just for building apps and testing them (on a Mac, I believe). So they didn’t really make their promised February 2008 for release, but at least there is progress.
I’ll be spending some time with it and I’ll be particularly interested in comparing the software distribution options for iPhone vs. Symbian/Nokia. Could it be that we are actually headed toward a situation where the only open platform is Windows Mobile? How ironic would that be?
Symbian Signed Followup
Bruce Carney from Symbian was nice enough to comment on my earlier “Why Symbian Signed must die” post.
There is no intent to prevent long term access. The Symbian Signed infrastructure hit a step change in demand. In periods of overload we have a policy to prioritize the service to ensure professional users can continue their work.
– The problem is shown in this link (i.e. a massive spike)
http://www.alexa.com/data/details/traffic_details/symbiansigned.com
– The underlying reason was posted in our developers forums here https://developer.symbian.com/forum/ann.jspa?annID=36
– Free Developer Certificates *already* downloaded over the past years are valid for 3 years, There are millions and millions of developers who *are* not being impacted by this outage.
– We have been trying to contact the developer of RotateMe to get the app signed (for free) and awaiting response?If anything, this underscores
(1) How Symbian OS is around an order of magnitude more popular than iPhone or any other mobile OS.
(2) As the smartphone OS market leader, Symbian OS is solving real world mobile developer problems every day, not preaching to the faithful on podiums with powerpoint.We just ask our developer community to be a little patient
Bruce Carney
Director, Developer Programs & Services
Symbian
Thanks for posting, Bruce.
I’m sorry I missed your call and I hope you are able to call back.
It’s great news that Symbian intends to restore the ability of people to get devcerts. And I understand and have read all the reasons and reported causes for the Open Signed outages.
I also agree that the volume of certs does suggest the popularity of the platform.
However, all that misses the point. The Symbian Signed server being down is just a symptom, as is the load on that server caused by the volume of developer cert requests. People are requesting so many certs because the signing restrictions are broken. The problem isn’t that the Symbian Signed site is down – the problem is that people have to use it in the first place. The problem is that apps need to be signed to be installed and the mechansm for freeware developers, or even small-time corporate or in-house developers, to get certs and manage getting apps signed (and tested and “approved” by Symbian) is defective. It’s untenable.
This is how we end up in the situation where developers release the apps “unsigned” and have the users themselves sign them (and thus, the high volume of “developer” certs). The arguments in favor of the signing requirement are about making phones “safe” and ensuring users can “trust” the apps. However that trust model is antiquated 20th century thinking. Look what they have to go through now to try to get freeware installed (getting a “devcert” and signing the freeware apps themselves). If they are willing to sign it themselves, it suggests that they “trust” the app, even though it has not been “blessed” by Nokia or Symbian. Why? The reason people trust these apps is not because some authority in the sky, like Symbian Signed, gives it a “thumbs up” but because the community provides a powerful degree of trust. Applications that jack around with people would be immediately discredited by the Symbian freeware community – everyone would know about it, and people would avoid the app like the plague. This works with things like Linux and Firefox and it would also work with Symbian freeware.
The current Symbian Signed process creates the opposite effect of its stated objectives. I’d suggest that Symbian Signed apps are actually less trustworthy, in the true sense of the term – it’s more likely for “official” apps that have been “approved and tested” to have bugs than the freeware ones because it takes months to get an app tested and approved (and it cost $$$) so bugs never get fixed; whereas problems with freeware get reported all over the place and they tend to get fixed quickly.
The solution is to release a version of S60 3rd edition that lets those users that are willing to take the risks install unsignd apps and grant the features, privledges, capabilities they wish to the apps, even if this is a “unsupported” “hacker” version of Symbian with “forfeit all rights to support” restrictions or some such – that would still be vastly better than the situation those people have today, where the only officially supported options are to not install the apps at all, ever or switch platforms/phones – and the “unofficial” solution is to overload the Symbian Signed site with “developer” cert requests.
So save yourself some money on upgrading the Symbian Signed server crypto hardware and instead release a simple version of S60 3rd edition. You’ll be happy, I’ll be happy, and users will be happy. And your phone manufacturer customers like Nokia will be happy too, happy that they don’t lose their customers to Windows Mobile, the iPhone, or other alternative platforms.
T-mobile offers Vonage-like service
Last year, T-mobile introduced a Wi-Fi calling UMA service called @Home, a mobile handset-based service. The idea was that you would use your mobile handset exclusively as a replacement for a standard home phone. The selling proposition of this service was basically (1) no in-home GSM coverage problems (because calls use wi-fi/broadband in the home), and (2) “unlimited” (domestic) calls from at home or at wi-fi hotspots.
T-mobile is now introducing a variant of that @Home play called Talk Forever Home Phone. It is an add-on service for T-mobile wireless customers that essentially provides a Vonage-style replacement home phone service. You get an ATA/router with a standard RJ-11 phone jack output to connect to a standard touchtone home phone.
The Talk Forever service is available as an add-on to an existing T-mobile plan and cannot be purchased separately. It is priced at $10 per month. This should put significant downward pressure on Vonage and AT&T CallVantage. But before you get too excited, note that this comes with the usual cell phone fine print and red tape – specifically there is a two-year agreement required and a $200 early cancellation fee! It also has unspecified taxes and fees.
With the advertised $10/month price point, one has to wonder if it might also impact Cable VOIP which has seen strong growth at a $40/month price point.
At the moment the service is only available in Seattle and Dallas. One thing not talked about with this service is international calling rates – if they are the same as normal T-mobile mobile prices, then this service will not be a competitive threat to other VOIP services in that regard.
Standard touch tone home phone
I think this move by T-Mobile of offering a “home phone”-based service shows that T-mobile has discovered through their experience with the handset-only first generation of the @Home service that there is a customer segment out there that is more comfortable using a ‘home phone” in the home, rather than their mobile handset. Here are some possible reasons why:
- missed calls because the cell phone was on silent or vibrate somewhere.
- cell phone is turned off to conserve battery power
- accidentally leave cell phone at work and find yourself without a home phone for a night
T-mobile has no wireline assets in the US, so clearly this is a way to attack Verizon and AT&T for the household user experience. It will be interesting to see if any other pure-play wireless carriers make similar moves.
iPhone SDK promised date approaching
As many may recall, Steve Jobs had announced in October that Apple would be releasing its much-anticipated iPhone SDK (Software Developers Kit) before the end of February – I’m certainly not going to let them forget it.
Rumors are flying as the final days wind down. Some say it will happen next week – others say it will be delayed. One has to hope that Apple doesn’t follow in Nokia’s Symbian Signed disastrous ways. if they do, I guess we all have to become Windows Mobile developers or wait for Android.
Why Symbian Signed must die
With the latest S60 “3rd Edition” phones (such as the N95, N81 etc), Nokia in their infinite wisdom, has decided for us that we users don’t want to install “freeware” apps any more. These phones now require all apps to be “signed” – they don’t give the option to the user to install an unsigned app.
Nokia says this is supposed to protect users from “bad” apps. So what is the result? Freeware developers now release “unsigned” versions of their apps and provide step-by-step instructions for users on how to get their own “developer” cert and sign the app themselves.
See the irony yet? Nokia told us that users wanted to be “protected” from “bad” apps, yet what we really see is users going to the trouble of acting like “developers” so they can sign these “bad” apps and get them installed on their phone. They clearly want freeware, whether it’s officially “approved” by Nokia’s “Symbian Signed” or not.
And with all these pseudo-developers requesting certs so they can install these “bad” apps, guess what? Nokia’s certificate creation site “Symbian Signed” can’t handle the load. It has been mostly down for weeks. Here’s what it says today:
Not to mention all the support costs for Nokia and the overall costs to the entire ecosystem (where about 90% of S60 3rd edition discussion seems to be about signing and certs). Hopefully Nokia will wake up and put an end to this ridiculous nightmare soon. Here’s a few reasons why the time has come for enabling users to install unsigned apps on their 3rd edition phones, just like they can on 1st and 2nd edition phones:
- The overhead of depending on Symbian Signed for signing promotes bug-ridden software that is never updated.
- It is destroying the Symbian third-party ecosystem (which is where all the best Symbian software has always come from)
- It leaves the door open for competitors like Apple, Microsoft, RIM, etc. and dilutes Nokia’s significant lead in third-party developer support.
- If plain users, through step-by-step guides, are signing apps, there is really no argument for the “all apps must be signed” restriction
The signing debacle is nothing new, but the prolonged downtime of Symbian Signed is.
Nokia, please. It’s time to close the door on the the Symbian Signed experiment and let us install the apps we want on our phones again.
UPDATE: Monday February 18, 2008:
Today the site says:
Note their words “huge demand for developer certificates”. Nokia doesn’t that tell you something? And by the way, it is Monday February 18, folks, and the ability to get certs is still down.
UPDATE: Weds Feb 20 the saga continues:
So now it looks like end-users and hobby developers cannot get certificates at all, meaning they cannot write code or experiment with freeware on their Symbian S60 3rd edition phones anymore. I cannot tell from the above message whether this the new permanent policy or just more “damage control”.
Reviewing the Nokia N81 – a teenager’s perspective
[Editors note: When I was asked to look at the N81, I decided, since Nokia is targeting youth with this new phone, who better to review it than my 16-year-old son. Thus, what follows is his opinion of the N81 8GB]
When I first got the Nokia N81, I was pleased at its sleek look and relatively nice size. Its weight is a little on the heavy side but that does give it that overall Nokia “tank of phones” feel which I like, as opposed to the awkward skinny light phones whose purpose of being small and light is totally countered by the fact that you are so scared of dropping the tiny piece of plastic, that you have to go out and buy a massive cover that defeats the purpose of having a small and light phone anyway. The Nokia N81’s interface is the classic Nokia [Symbian Series 60] interface which I am a big fan of and I enjoy that Nokia keeps a constant user interface rather that scrapping it every time so you have to learn how to work a whole new type of system with every new phone.
The battery life on the N81 is rather impressive, going for roughly three days without needing a charge.
The phone has a N-gage application, which from playing the demos, looks solid but I cannot picture anyone who would really buy the actual games and not just play the demos to death. The fact that Nokia is now trying to incorporate one of the most failed gaming systems in the history of man back into their phones makes me chuckle at how horribly N-gage failed in the past and how imminent its future failure is.
The music player is quality and simple, operating very similarly to an ipod. Nokia does not yet offer the downloadable software for the N81 that allows it to sync with itunes, so I had to place music on the phone by plugging it in like a flash drive and dragging and dropping songs into it. This method is tedious but works fine and I have full confidence that the N81 software will work just fine when it is released. The likable things about the music player are that for a phone, 8gb is pretty large and definitely enough to have a good selection of music. My favorite feature of the music player is that it takes a basic headphone jack. Most phones require that you buy an adapter or use the strange uncomfortable ear buds that come with the phone but being able to plug any old headphones you want into the jack makes it seem o-so-much better. Oddly enough, the music player also has one of the least thought through features I have ever seen, which makes operating the phone insanely frustrating. The aforementioned problem is the combination of small buttons and the fact that the play button works no matter what else the phone is doing. The play-stop-pause-rewind-etc. buttons encompass the up-down-left-right buttons. So when navigating around the phone, it is easy and almost unavoidable to hit both up and play at the same time because both buttons are so small and so close together. Now normally, no harm no foul, you’re not in the music player so nothing should happen – but since Nokia always has to have one massive flaw that was probably thrown in thoughtlessly towards the end of production, no matter what you are doing, the play button still plays music and since the speakers are rather loud and startling when you did not plan or even think that random music could suddenly stream from your phone, it is often an embarrassing moment when you are trying to text whilst walking down the street and Hardcore gangster rap blasts out of your phone unexpectedly. This is something I have yet to learn how to fix. This dilemma continually frustrates me to no end and is the only thing that would make me consider not using this phone.
I’ve discovered several things with the N81 that I consider bugs that could use fixing. The first is that the phone has trouble finding service and once service is lost, you have to turn the phone off and back on for it to start searching for service again. This bug is surprisingly not as inconvenient as one would think, although the phone would be greatly improved if this was fixed. The only other bug that is worth mentioning is that text messages sometime take five to ten minutes to send or be received causing you to seem rude for taking too long to respond [editor: that may be T-mobile]. Other than that, it has no actual effect being that eventually the texts get sent or received.
The N81 is a good combination of the classic, simple “Nokia sturdy brick” and the advanced little flashy features like music or gaming that make a phone sell these days. Overall the Nokia N81 is a quality phone that has potential for excellence, with the right subtle tweaks.
