You Are Here:

Community: Blogs

Gabor Torok's Forum Nokia Blog

MoMoHu - Telco to Web by NSN

tote_b5 | 05 May, 2009 19:39

Damn, so many abbreviations, let me elaborate them.

Mobile Monday Hungary has had another round yesterday with Nokia Siemens Networks giving presentation about Telco to Web. The event was also hosted by NSN at a nice place at their premises.

After a brief introduction given by Robert Esik, there came the "real" presentation about the main topic presented by Said Berrahil. Said's presentation skills are really fascinating and it didn't take a minute to hear the first laughs from the audience.Funny, still serious, informative and thought-provoking. The whole presentation was built around the seven deadly sins, which the operators have committed so far. Don't take it that seriously, though: lust, gluttony, greed, sloth, wrath, envy and pride were all mentioned and with the obvious exception of lust some examples helped us understand what network operators did wrong.

Achievements were also mentioned, though! Since it's naturally not only bad things that operators have done so far. It's even more understandable that achievements were highlighted from a company whose main customers are the operators themselves, right? :) I found it a bit odd, though, that after talking so much about operators' business (don't forget that NSN is not an operator!) Said didn't talk too much about what they had been doing lately.

Finally there was a half an hour free Q&A session after the presentaion where people were really active to talk about the topic. I was surprised to see so many people (35-40) interested in such a not-so-popular topic and have heard lots of good and insightful comments.

Looking forward to the next event!

Tote, a co-organizer of MoMoHu

The $1 business model

tote_b5 | 23 March, 2009 02:08

There are two kinds of developers: those who want to sell their programs and those who write software for fun and/or for fame. The latter type is happy with writing freeware, most probably open source software. This article is about the former.

Of course, most developers want to get paid for their programs. As much as possible. The wiser usually analyses the market first:
  • Would people be interested in the program?
  • Would they be willing to pay for it?
  • How much will they think the program is worth?
  • What about competition, would our program fill a gap or it would just be one of the many?
  • How can I sell my program, what distribution channels are available, what is the revenue share, etc?
  • How much do I need to invest in writing the program financially, in terms of effort, etc.?
And the list is not over yet. But it contains the most important question from this article's point of view: how much is a program worth, how much can we ask for it? Note: the answers to these questions are not necessarily the same.

It is very difficult to foretell how much a program is worth for the users. The answer depends on so many factors, such as target group, their spending habitstype of software (e.g. leisure vs professional), what other programs with similar feature-set cost, etc. Naturally, price calculation is so often affected by that how much a developer appreciates his/her own software ("I put so many hours in creating it that it can't be cheap!") - and the expectations and the reality are not always in balance.

The available distribution channels also influence the final price: what they demand from the developer, what they offer to him, their revenue sharing model, etc. As to the latter, for example, although the 70-30 revenue share wasn't typical 1-2 years ago it is now becoming a standard. Apple's App Store, OHA's Android Market, Nokia's soon-to-be-opened Ovi Store all offer 70% off the revenue to the developer. Revenue share is not everything, though: for example, App Store is such a place where it's not uncommon to hear success stories and big earnings, whereas Android Market's community prefers free software. If you follow the news, you might have heard of the coming BlackBerry App World. I found it very interesting that they set the minimum price for a paid-for application to be $3. They said any software that is not worth this amount shall be freeware. I think it's ridiculous: these guys are not aware of how many developer they will alienate from themselves with this approach. Do they really want developers to sell BB apps or not?

The typical revenue models for developers are as follows:
  • Release free application first with limited features and make it paid when it really gets traction (thousands, tens of thousand downloads per month). The application is available either for free or as paid-for (exclusive OR). Question: won't people turn away from your application once they have to pay for it?
  • Write an always paid program, which means that your application must be really cool and advertised so well that despite the price (i.e. that it costs money) people buy it. Question: can you compete with free programs with similar features?
  • Make a Lite and Pro version of your program, Lite being free and Pro paid. The free version supports a subset of Pro's features making it compelling enough to purchase the paid version. It is a very typical approach among developers. Notes: increased maintenance efforts + separation of free and paid-for features must be well thought-out.
  • Free program with adsNotes:
    • Not all people like ads
    • You need to find a good ad provider
    • It is challenging to implement a good advertising solution on mobile devices, and there is no good framework available.
  • Change model dynamically on an experimental basis: see if you can make it with paid version, if not then make it free, then make it paid again when it becomes popular (this is the path iStrip followed, actually). Question: when will people get bored with this behavior?
Please note that I did not include that model in the above list, where the client program is free, but it is essentially a light-weight interface to a server solution, which is exactly what your customers are paying for. Opera Mini's business model is based on this, for example: Opera Mini, the application, is available for anyone as a free download, however, it's Opera's customers (i.e network operators), who pay the price. This article is simply not about this model.

It's also worth noting how important user ratings have become recently. Some developers faced that ratings can kill: unhappy-uneducated users gave low ratings just because "game was too short", they "expected more", "it was free not too long ago", etc. Perhaps these users are not aware of how much power they have in their hands when they rate. Applications written for Android platform and distributed on Android Market are especially vulnerable to this effect. 

Finally, getting closer to the point: how much can we ask for a program? Even though this habit is changing, it's still quite typical from people that they think that "cheap cannot be good" or "if it's good it can't be cheap". However, App Store's success stories have proven right the opposite: developers claimed that their revenue had become much higher when they lowered the price to $0.99. You know, this is such a low price that basically anyone can afford around the world even for the silliest programDevelopers are now facing the fact that unless they sell their software at the lowest price there will be others who ask less than them. This basically forces them to sell their apps for $1 from the beginning.

Is it the final price, though? Can a $1 hit be sold for $2, too? No-one knows. It's all about making experiments. If I were to sell my app that I think is worth more than being distributed as a freeware, I would ask $1 for it. If people don't buy it at this low price, then I saved the hassle of price calibration. If it gets successful and my program is (one of) the best(s) in its category, then I would increase the price gradually until the download rate gets stabilized and I couldn't expect more revenue from making it even more expensive.

And actually this is what I call the $1 business model.

Looking forwad to your comments,

Tote

Smartphone statistics, 2008

tote_b5 | 12 March, 2009 17:16

Gartner released their statistics about worldwide smartphone sales, which contains useful information not only the previous quarter (Q4 2008), but the whole past year. I'd like to share the following two figures with you:



Comments:
  • Nokia is still #1, but it's market position is seriously challenged by RIM, Apple and HTC.
  • Even Apple is suffering from decreased sales in Q4, but that didn't prevent them from being ranked as the third vendor by sales.


Comments:
  • Symbian had lived better days a year ago, but it's still a bit more than 50% of smartphones that runs this operating system.
  • RIM and Mac OS X performed exceptionally well even during the tough economical situation.
  • Although the share of Windows Mobile shrank a bit, it still maintains its third position. Only blinds can't see that not for long.

Finally, some words on regional sales:
  • Dramatic increase (69%) is experienced in sales of smartphone in North-America, which now accounts for 20% of mobile phones in this region. Carriers are agressivelypushing data plans that is beneficial for vendors, too, offering vertical mobile solutions from hardware manufacturing to providing developer SDKs to cloud services.
  • While overall device sales dropped, Asia/Pacific recorded a 2.3% growth in smartphone sales.
  • EMEA region were up by only 2%, Western-Europe sales increased by 9.6%. Samsung drove sales in 2008 with Omnia as its most successful product.

Tote

Mobile advertising - An experience

tote_b5 | 04 March, 2009 10:51

Background

I decided to give a try to a Reversi-like game found on the Internet just the other day. There was a link to an installation package, which I downloaded and manually installed on my Nokia N95. Even though there was nothing mentioned about that the application is ad-supported, I found the name of the program suspicious since it revealed something about this fact. Never mind, I thought I would still give it a try even though I don't like suprises that come in the form of embedded installation packages (for non-Symbianers: an installation package can contain other 3rd-party software, too, which the main application depends on - these additional programs are referred to as embedded installation packages). Nevertheless, the complementary software has become so intrusive during the installation process and wanted to know such information about me (surprise: it gave me a default birth year, which was exactly the year I was born in - was it an accident or it could find it out somehow?) that I was unwilling to give. Finally I gave up the installation with some bitter taste in my mouth. That was my first experience with Adtronic.

As to mobile advertisement
It's a cliché that there are three-times more mobile devices than desktop computers. If people believe that desktop computers are the homeland of Internet and advertising they will soon have to realize that the transition has already begun from one to the other. Undoubtedly, a device that is always with us is much more compelling platform for advertisers to reach their audience. Their are challenges, though:
  • Generally the 'context' is an invaluable piece of information from advertising's point of view:
    • What is the user's location so that those ads will be shown first that are more relevant at that place.
    • Any kind of information can come in handy regarding the user's social network (gender, age, habits, relation to user, etc.) for better targeted ads.
    • What the user really wants to do in the given moment, such as browsing to a car rental web page, calling a carpenter, receiving a status report SMS from the bank, etc.
  • Mobile phones has different characteristics as desktop computers: one of the most notable differences is that they have smaller display giving less room for nice ads that can easily capture the user's attention.
Questions to the 'Audience'
There are couple of things that even I, as a advertisement target, have to answer. The root question is the same in all cases: How much am I willing to give up from my freedom when using my beloved gadget?
  • How frequently may ads appear without disturbing me?
  • How much should I let the ad-provider know about my context?
  • What can an ad do without being too intrusive?
  • Is it a single application that is 'ad-aware' or I let my entire phone user experience be 'ad-driven'?
Adtronic
Based on what I wrote above you can imagine that I classified Adtronic software as 'suspicious'. But I was surprised to read Forum Nokia Newsletter this morning giving fame to Adtronic. Was it early to judge this software, I asked. A brief summary to those not wanting to visit Forum Nokia:
  • Adtronic offers advertising solution for S60 devices.
  • Ads are shown upon new/missed calls, SMS, MMS. Ads usually appear above alert dialogs covering the majority of screen real estate.
  • How many ads are shown a day can be limited by the user - one must not count on a lot of earned points if it's severely limited, though.
  • Earned points can be used in various ways
    • For reduction of phone bill (who will take care of this?)
    • Points can be used to purchase other applications at a discounted price
    • Or can be redeemed for GreenPeace, Unicef (nice feature)
  • The whole solution relies on a working network connection resulting in some data traffic (how much?).
Adtronic offers better monetization to developers should they allow their applications to be bundled with this service. May I ask, though: is it really the price users (not the developers!) have to pay to use applications at a low price? Am I wrong with that selling $0.99 programs also works in Apple's App Store and I bet it will soon work on Android Market, too? Do we really need this?

Another question I'd like to be answered, too: where can I use my points to purchase applications? Is it Adtronic's own store? Or an operator store? How does the whole idea fit into the model of unified content store that all device/platform vendors are pushing lately?

I'm sure I've missed a lot of points with regards to the topic. Could you please make the picture clearer? Thanks!

Tote

Mobile Monday Budapest - Great success!

tote_b5 | 24 February, 2009 16:35

We held the second Mobile Monday Budapest event yesterday evening. As I already wrote, the topic was mobile software developmentAndroid and Symbian in particular. My colleague gave a great presentation on Android and I talked about Symbian. Unfortunately, the third presenter was not able to come, thus we didn't have a presentation about iPhone development. Nevertheless, we still tried to cover as wide range of platforms during the free Q&A session as possible.


There were something like 50 engineering-minded people (like us:), brave enough to ask smart questions, eager to learn from the others (not only from presenters) and willing to network. The event was sponsored by Forum Nokia (event site is available at bantora.com) and my employer, Agil Eight. Thanks for both!

I'm so happy that this habit slowly becomes a tradition - it's exactly this what we need in our small country. Looking forward to the upcoming MoMo Budapest even in April!

Tote

Mobile worm, Yxes.A - an analysis

tote_b5 | 20 February, 2009 11:58

F-Secure and FortiGruard both reported that a new worm,Yxes.A, is spreading on Nokia smartphones based on S60 3rd Edition platform (and probably higher, too). According to FortiGuard:

  • "It gathers phone numbers from the infected device's file system, and repeatedly attempts to send SMS messages to those. The messages feature a malicious Web address (URL); upon "clicking" on the address in the received message, the recipients will download a copy of the worm (provided their phones/subscriptions allow for internet browsing)." That is, it's a Trojan.
  • Beyond propagating to as many users as possible via the strategy mentioned above, the worm's aim is to gather intelligence on the infected victim (such as serial number of the phone, subscription number) and post it to a remote server likely controlled by cyber criminals.
  • It's also noted that  worm can mutate easily: "As far as our analysis goes, the worm currently does not take commands from the remote servers it contacts. However, since the copies hosted on the malicious servers are controlled by the cyber criminals, they may update them whenever they want, thereby effectively mutating the worm, adding or removing functionality." It's not that simple, though. It's not like download a new EXE from the Net and it will just work. No new EXE or DLL (a plug-in, for example) can be installed without the assistance of Application Installer, which will eventually require user's attention and approval. Some files that don't have to be installed can be downloaded, though, containing instructions for the worm to execute, however, it's becoming a science fiction if we think that any malware author will put THAT much effort in developing such a system. I'm highly sceptical on that it would be a real threat and refuse to be threatened by that.
  • It's also reported that "On launch, the worm executes as the process 'EConServer.exe', which is likely meant to camouflage alongside the existing legitimate system process 'EComServer.exe'". This simply doesn't mean anything: if a process name is only similar to another (system) process name then it doesn't imply anything. And anyway, EComServer.exe is never launched by hand (but by the system upon device start), consequently it's not a valid scenario that the malicious EXE gets launched instead.
  • It's a very agressive application, since it "will also automatically run every time the device is rebooted / power cycled. Further, it bears a destructive nature and will kill certain processes such as the application manager (AppMgr)." If that's true then the program must hold very strong capabilities that cannot be granted by a self-signed certificate.
You can see from the list above that the worm can be malicious, indeed. Following from the last point we can conclude even more:
  • The program couldn't be self-signed, since the program requires such strong capabilities that the Application Installer will never grant to a self-signed installable.
  • It couldn't be signed via Open Signed Offline*, either, since that would limit the spread only to max 1000 devices with given IMEI numbers.
  • It couldn't be Certified Signed*, either, since that requires a thorough test done by an official Test House. Even if they hadn't done a thorough test, such a behavior must have turned out very soon.
  • All that means that it was Express Signed*. You know, one characteristic of Express Signed is that they do occasional testing, which means that there might be some malicious apps that can go through this filter.
What counter-measures can be taken? First, the certificate of the malware author must be revoked. That means that whenever they will try to publish another application, whatever it will do it will not be allowed to be distributed, but will be filtered out automatically. This doesn't comfort any victims of this virus, though (hmm, are there any?).

Second, it would be just great if OCSP-checking was enabled on every phone by defaultOCSP is a protocol that allows the Installer to check it in a database that a certificate is revoked or not. Although it is available on each S60 phones, it is disabled by default. But I go even further: it's not only the Installer that should use it, but other components of the system, too. In fact, the system itself should perform such a cross-check at regular intervals if any of the installed applications have become undesirable for the user (i.e. the certificate used to sign that application has got revoked) in the mean time. I'm unsure as to why this mechanism can be disabled at all, probably because it requires a network connection and data exchange with a remote server. But I think this should be something that operators shouldn't charge for - isn't it in their best interest, too, that the devices using their network wouldn't get infected?

* For more information on various signing schemes, please visit Symbian Signed.

Any thoughts are welcome,

Tote

Mobile Monday Budapest - Mobile Software Development

tote_b5 | 16 February, 2009 22:36

It's time for the 2nd Mobile Monday Budapest event! This time the topic is mobile software development and we selected the three hottest platforms: iPhone, Android and Symbian. I wrote 'we', because I'm among the organizers as well as one of the presenters: my presentation will cover Symbian-based development.


Some information on the event:

Date:  Feb 23, 2009
Time:  18:00 - 21:00
Venue:  BUTEMagyar Tudósok Körútja 2Room 019

For more information, please refer to Nokia's new web service, Bantora, or Mobile Monday Hungary.

Everybody is welcome!

Tote

Malware on Android: It has begun

tote_b5 | 27 January, 2009 22:46

No, it's not going to be yet-another I told you so post. Though I did. :) You might have heard of the spreading of MemoryUp virus on Android-powered devices. There are numerous articles mentioning it (like this one ;), let me cite one of them from phoneArena:

"As strange as it may seem, a lot of users have complained of the MemorUp app..."

What is so strange in this? Android's security model is an open invitation to malware authors: anyone can write an application and distribute it freely on Android Market. The secret is that although every application must be signed, it's not mandatory that the certificate used for signing be certified by a Certificate Authority. In other words, you can self-sign your own application.Accountability is lost.

"We’re more worried about the fact that such a harmful application has found its way to Android Market and has stayed unnoticed until now."

That's exactly how Android Market works. I'm surprised that you're surprised. Anyone can write and freely distribute their own programs that may even be a malware. Signing ought to prevent from mass virus distribution - as long as signing certificates are certified by CAs (authors can be traced back and prevented from continuing malicious activity). Which is sadly not the case, see above.

"If it has managed to creep inside, wouldn’t there be a chance for others?"

It's not a question, I'm sure there will be more. Even though self-signed applications are limited as to what they're allowed to do, MemoryUp has showed us that this restriction is not enough.

The question is rather what could be done against this phenomenon? One option is that Google leaves it untouched: it will turn out very quickly if a program is malware or not (well, unless if it's a timed bomb). Another alternative is be stricter on what a self-signed app can do and allow only properly (i.e. CA) signed programs to act freely (after user's confirmation, of course). The strictest option would, of course, be if self-signing was not allowed at all. I'm sure you've noticed that the last two options mean that developers would need to pay for (CA) signing. Which is against the principles of Android development.

Looking forward to Google's reaction,

Tote

MicroWeather for S60 goes Open Source

tote_b5 | 22 January, 2009 10:23

I usually don't write about specific mobile software, but this time it's a bit different. You know, it's one thing that one of my colleagues, Jouni Miettunen, became a Forum Nokia Championlast time thanks to his active participation in Python for S60community. I'm really proud of him, he really deserved the honour.

But it seems that the spirit of open source software has "infected" another colleague of mine. Gabor Fetter, author of MicroPool (a bestseller in its category), MicroPinball and MicroWeather has now decided to make his last piece of software open source. I'm not going into praising MicroWeather, let it be enough that I use it daily. For more information, you can check out the official page at http://sourceforge.net/projects/microweathers60/. But you can do more than being in read-only mode: why not contribute to it? Any ideas, contribution are welcome!

  MicroWeather - City List MicroWeather - City details

I'm happy to see that we're that agile! ;-)

Tote 
mobile-thoughts.blogspot.com

What is the world's most recognized song?

tote_b5 | 19 January, 2009 23:10

Thanks to the Carnival of Mobilists and more importantly the great analysis from Tomi Ahonen I learnt where the original Nokia tune is from. I'm not a tune-addict, still I can't stop listening to this one. Enjoy!

 

Tote 

mobile-thoughts.blogspot.com 

Thoughts on Palm Pre

tote_b5 | 14 January, 2009 11:19

Of course, I've seen Palm's keynote from CES 2009. I've also read quite a few blogs, comments on the topic and now would like to share my impressions about it.


First of all, I liked the device! It looks great, the addition of a QWERTY-keyboard makes it even more complete. The UI looks intuitive, I pretty much liked the introduced card system, where you could switch between running applications. In general it's a fancy device with a high WOW-factor.

Then, what else? Well, my first impression was that it's a copy device, an iClone. It's just a better iPhone, not as if it was not a remarkable thing alone. Nevertheless, I have a few questions on copying a bestselling device in general:
  • Is that allowed to sell a very similar device with some enhancements? I'm pretty sure that Apple patented a lot of things and I'm surprised to see the same multi-touch functionality to be present in Palm Pre, for example.
  • Is that nice? Does it make good to Palm's reputation that everyone knows that "iPhone was the first"? I'm pretty sure, though, that Palm will not feel sorry if it's profitable and legally okay.
  • Will this strategy work at all? As Michael Mace greatly puts it: "... Pre is a better e-mail device than the iPhone and a better consumer device than a Blackberry ... [but] it's probably a worse entertainment device than the iPhone (because it doesn't have iTunes) and probably a worse e-mail device than RIM (because it doesn't have RIM's server infrastructure)." The thing is that we don't know too much other than a technical specification. How much will it cost? What services will be available for the user? In general, why users will want to buy Pre instead of other competing products? And lots of other questions, partly covered below.
I wonder how it will work out that Palm is fighting against such competitors who have existing products in their portfolio. Pre is said to be available in H1/2009 in Sprint's network, but no news about pricing policy, international availability, etc. yet. If Palm will be able to ship this product with such a great technical parameters, their top-priority will (have to) be to build an ecosystem around it. That most importantly means services that 1: give Palm post-sales revenue and 2: tempt users to choose rather Palm's device than any other competitor's. In addition to that, developers must be inspired to make great applications that boost 3rd-party business, too.

In fact, development on Palm is a big question mark to me. You know, I've never been into Palm development, but what I've read from others on this topic was that 1: WebOS is a completely new software architecture, 2: with no backward compatibility. In other words, old applications will not run on the new device. I mean, it's not only that you have to make some tweaking on your existing software and then it will run in the new environment (think of the introduction of Platform Security in Symbian and what that meant to old software), but you have to completely re-write it and even then it's not guaranteed that it will work. Why? Because the keyword for the new SDK is that it's about web-development. Palm toed the line by supporting WebKit (their browser is based on it) and it's great that there's a common platform available on most smartphones by now. Well, Microsoft still resists and I bet that they will always do. In general that means that the boundary between mobile- and full web becomes more and more blurred, but that alone doesn't give you the promise of "Mobile development Paradise". Why? Because you simply can't solve everything with the HTML/CSS/JavaScript trinity. How will you develop your own VoIP, image processing, gaming, etc. application with this technology stack, for example? It's simply not the right tool for a lot of things in software development as in fact no one technology stack can be. But if you limit yourself to one then you eventually shrink your software market. I'm not saying that it will be the only way for development in the future, however, at least it was the message that I got from the keynote.

Finally, two features that captured my attention for different reasons:
  • Multi-tasking, i.e. being able to run more than one application in parallel. Everybody is keen on that and points out that how great it is compared to the iPhone. And then what? I think it's not an innovation at all - I would say that what's the innovation in the 21st century of NOT being able to do that. Damn, Apple was better again in doing that. :)
  • Card-system. Everyone who's seen the keynote or any preview can tell that it's about accessing simultaneously running applications: different apps are shown in a list as playing cards and can be manipulated in a very intuitive way. No doubt, it's a great idea and I'd be happy to use it on other phones, too.
Comments are welcome,

Tote

Predictions for 2009

tote_b5 | 05 January, 2009 02:44

I'm only a little bit more experienced in predicting future trends than I was last year, still I'd like to continue what I started a year ago. Who knows, maybe I'll be at least as right as I was last year?
 
Let's start with reviewing what I wrote previously and what really happened in 2008:
  • I commented on ad-driven content and how much e.g. Google depends on operators in allowing their users to use the Internet at a fair price on their mobile. Well, it was only a concern that I raised, but Google's (and Apple's) move was brilliant: they showed that it is not impossible to change the rules. What I really mean is that both companies have their phones offered by network operators with a flat-rate data tariff (it's according to the agreement between the handset vendors and operators), which is really the way for free Internet usage.
  • As to NFC, I disagreed with the statement of one of my fellow champions, Paul Coulton, that 2008 would be the year for the rise of this technology. I now think that I was right in this question: this technology had so many challenges (let it be technical or political between banks and operators, for example) that 2008 would have been too early for the rise.
  • Touch - I have only seen the hype around Apple's new phone at the time of writing my previous prediction, but even the early signs were enough to predict that other manufacturers will try to copy Apple's successI was right in this, but of course, having only this new feature is not enough for success, though obviously is a mandatory component in the recipe of success.
  • As for Java and that it would be becoming more popular again on mobile platforms, to be honest I can't see any measurable change today. Okay, Android development environment requires mostly this knowledge (not to mention Brew), however, this platform is yet too young to have significant influence on Java's success.
  • Awakening of North-America to smartphonesit DID happen. People on that continent has finally realized that there are other features that a mobile phone can offer, there are other services that they can use with their favourite gadget, and in general there is much more that they can do with their cell phone that they could ever imagine. And since North-America is in a very strong position when it comes to technology, the awakening of people living there will surely give a boost to innovation and further spread of smartphones.
  • Finally, I wrote that manufacturers who really think in big will not only sell phones, but also provide Internet services to users. This has also become true, although this will be a never-ending process currently with two-kinds of players: one that has already proven on service-front (e.g. Apple, Google) and the other which is already a recognized brand in mobile (e.g. Nokia).
What will happen in 2009?
  • Most importantly: the trend will continue for smartphones to become a commodity. Despite the financial crisis more and more people buy smartphones as they become more affordable (mostly due to binding contracts, though prices get lower, too) and once users get used to advanced features they'll be reluctant to give up using them.
  • As to advanced smartphones with binding contracts, the two newcomers, Apple and Google, managed to achieve that their devices are sold in a contract with flat-rate data tariff. The obvious effect of this is that users will use the internet much more and will be online for much longer.
  • More services will become available, their integration is a key factor for handset vendors (NokiaLife Tools, Comes With Music, Mobile e-mail and mail on Ovi, etc.iTunes & MobileMe for AppleZune for MicrosoftGMail, Calendar, Docs, etc. for Android-powered phones, etc.). Thanks to these services network operators will be in a worse position to fight for users who not only purchase phones and pay monthly subscription-fee, but also willing to pay for additional services.
  • Touch still rules with such innovative ideas as gloves, multiple devices to share their resources, etc. Even more, touch display will not remain a smartphone-only feature, but other devices in the lower-segments will also be equipped with it (e.g. Nokia's first feature phone on Chinese market: http://www.mobilemonday.net/news/nokia-announces-shows-chinese-touchscreen-phone).
  • 3rd-party apps and app stores: we'll see the introduction of new and re-newed application stores with client integration. Commercial software can be downloaded as well as freeware, revenue share will be more advantageous for developers than it's been so far. The fact that handset vendors are providing their application stores, too, will cause hard times for such independent players as Handango, for example. On the other hand, the obvious advantage of these regular providers will not really disappear: the variety of mobile handsets for which they offer content is much bigger than the coverage of any of the new stores will ever be.
  • NFC - it seems the time has come for this buzzword to become more popular. In last November, GSM Association called for Pay-Buy-Mobile handsets so that NFC technology be built into commercially available mobile handsets from mid-2009.
  • Android phones spread all over the world: we have already heard about the second handset that Kogan, an Australian company will ship this January, but rumours have been told about HTC, Huawei and other companies, too, that there will be other phones based on this platform.
  • Nokia finally to gain more market share in North-America thanks to AT&T for seeing lots of potential in Symbian to become the main smartphone OS in their portfolio
  • Use of mobile phones in new areasNokia Life Tools for users at the bottom of the pyramid (mid-range, low-end phones mainly), Nokia Home Control Center for advanced users who wish their smart home to be controlled by their smartphone, etc.
  • Transforming smartphone market sharesMotorola, Palm getting weaker (former betting on Android, latter introducing yet another proprietary system), RIM, Sony Ericsson "to survive" (RIM closed a surprisingly good 3th quarter in 2008; Sony Ericsson is also giving a try to Android), Apple getting strong (iPhone Nano in the queue), Samsung remaining strong (very innovative company challenging Nokia, the leader, all the time), although Nokia's position gets slightly weaker, it still remains the most dominant player (one of the most versatile players in this arena with lots of innovation in different areas of mobile space), Microsoft to struggle (has any one of you heard anything about them lately?).
  • Open-source model to gain ground - license-free handsets, free development environments, high inspiration for developers & tech companies to help each other, etc.
  • LTE - let's return to 4G and LTE next year, okay?
  • WiMAX - don't expect mass adoption of this technology in mobile phones yet (though pioneers have already appeared in 2008)
  • Mobile TV - the future is still foggy: which standard to follow (DVB-H or DVB-T?), will people buy this service at all, etc.
Did I miss something? Sure. Can you correct me in anything I wrote? Anything to add? Please do! Thanks!

Tote 

The diversity of Symbian development

tote_b5 | 06 December, 2008 23:49

When talking about mobile software development lots of people forget about the fact that it's not only the native programming language that can be used on a given platform. I've read a lot of comparisons between Symbian/C++, Win32/MFC/.NET of Windows Mobile, Objective-C on iPhone, Android, etc. lately discussing the advantages and disadvantages of these options, maturity and popularity of the underlying platforms, probability of writing successful programs, etc.


The problem with these comparisons (in which Symbian/C++ is typically at the end of the list with its peculiarities and steep learning curve) is that they discuss only half of the picture. The more advanced a mobile platform the more you can do on it - which applies to software development, too. I strongly believe that one of the strengths of software development on Symbian platform is that it's not bound to a single programming language, SDK, etc. A lot of you might not know that for Symbian-powered devices you can write software in
  • Java - Mobile Java (JME) has been available since the early days,
  • Flash Lite - Adobe's Flash has been added to S60 phones 1-2 years ago,
  • Python Python for S60 is an open source initiative enabling rapid application development,
  • Ruby Ruby for Symbian is one of the newest additions to S60,
  • .NET - Red Five Labs's add-on to S60 platform is tempting Windows Mobile developers to use their skills on another platform,
  • NS Basic - Powerful development environment and run-time framework for programs written in BASIC (link),
  • HTML using other web technologies like CSS, Javascript - Apple's WebKit rendering engine is becoming the de facto standard for mobile browsers making them capable of showing full web pages (i.e. not only WAP or mobile web). This enables widgets development for a range of smartphones like S60-phones, iPhone, Android, etc.
You can see from the list above that Symbian development is much more than native application programming. On the contrary, I dare to claim that native programming is becoming less and less relevant over time. Of course, each option has its strengths and weaknesses (as well as native programming) the point is diversity, the possibility to choose. This (among others) makes Symbian OS's position stronger than its competitors': if you can develop for one mobile platform it's almost sure that you can use THAT knowledge for Symbian development, too. One exception for this might be Objective-C on iPhone, but I wouldn't be surprised if that became a reality on Symbian in the near future, too.

By the way, Simon Judge made a quick comparison between different platform development options - it's worth a read. As well as Andreas Constantinou's  post at Vision Mobile - a well-written article about mobile application runtimes for better understanding this world.

Any comments are welcome,

Tote

Nokia should buy Yahoo?

tote_b5 | 26 November, 2008 12:31

It's already known to most people that Yahoo! is in big financial trouble. Even worse, they were tried to be bought by a company (Microsoft) they didn't want to sell themselves to. They successfully fought against that attempt, however, their value was much higher at that time than what it is today. They were even "helped" to survive by a company that they normally call a competitor (Google). But this help didn't last long as Google was afraid of the consequences of a deeper relationship with Yahoo! (i.e. antitrust).


Now Yahoo! has an even bigger problem with much lower valuation. That, among others, inspired telecoms.com to speculate on whether it would be worth for Nokia to buy Yahoo!. Besides the fact that financially it would be a good deal for Nokia, they would even win a very popular brand (especially in the US!) for themselves. And all this along with that Yahoo! is very strong in (web) services would make their position much stronger against GoogleMicrosoftApple and the likes.

Putting aside the negligible fact that there's a world-wide financial crisis lately is this option not worth considering?

Tote
 
Update: El Reg reported that Nokia CEO Olli-Pekka Kallasvuohad answered this question during MWC 2008 saying 'no' to a possible acquisition of Yahoo!. 

Mobile Monday in Hungary

tote_b5 | 25 November, 2008 16:14

I don't know if you've ever heard of the event, Mobile Monday, but if you visit their site you can see that it's a global community of mobile industry visionaries, developers and influentials fostering cooperation and cross-border business development through virtual and live networking events to share ideas, best practices and trends from global markets.


Now it has finally arrived to Budapest, Hungary! I attended the very first event last evening and I was surprised to see how many people are involved and interested in mobility in this small country! It wasn't a very long event and there were only two presentations, but hey, it's the first one, right?

Actually I was interested in Torsti Tenhunen's presentation (Mobile Media – connecting and consuming everywhere) and was also wondering how many people have ever heard of Ovi, for example. Not too much as I could see in the audience. There was a Q&A session at the end of the presentation and since the audience didn't dare to ask anything (including me ... sigh), some people were randomly picked up to ask questions. I was picked up, too, and managed to ask a tough question. At least, even the presenter admitted that it was tough.

What was my question? Well, relating to Ovi I always wondered what Nokia's view on entering a competition with such big names as Apple and Google who have already proven in (web) services. My question was something like "How does Nokia intend to compete with those popular services that people have already got used to (iTunes and Google's bunch of services) and in general how do they see their position in the newdevices + services setup where manufacturers are rolling out their own services, too"? Well, I admit that it's not a question that's easy to answer. As I mentioned even the presenter admitted that. Of course. I like to ask tough questions. Anyone can ask easy questions, but not so many people can point out things that are behind a presentation. This was the first fullpresentation that I saw about Ovi (of course, I had already known a lot of things about it beforehand) and although it was a new concept to most people I wanted to know more.

To be honest, my question was only partially answered. Some marketing hype was included in the answer (we're good at services, people will buy the idea, because they're gonna be very good, we have our brand name, etc.) in addition to pointing out the fact that Nokia has nice programs for emerging markets (think of Nokia Life Tools). This argument is valid, indeed, I've even already discussed about it lately. On the other hand, my addition to this list would have been something like:
  • the coverage of offerings these companies offer (including Nokia) varies and that gives users the freedom to pick up their choice of service provider,
  • Nokia plans to set up its own MVNO in Japan (read about the consequences and how it's supposed to affect e.g. Ovi here).
Anyway, I'm happy to attend upcoming MoMo events in Budapest in the hope of stiring up the "local" water. With unpleasant questions if necessary. :)

Tote
 
1 2 3 4 5  Next»
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditFurlTechnocratiMagnoliaTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZrelationQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fschemasE2fnokiaE2fFNE2d1E2e54E2eowlX qdcZtitleQSxForumE20NokiaE20BlogsE20WebE20SiteXLen qdcZtitleQSxForumE20NokiaE20BlogsE20WebE20SiteXLen qdcZtypeQUqfnZE44istributionQ qdcZtypeQUqfnZSiteQ qdcZtypeQUqvocZTermQ qdcZtypeQUqvocZVocabularyConstructQ qdcZtypeQUqwebZSiteQ qdcZtypeQUqrdfsZE52esourceQ qswZserviceQUxhttpE3aE2fE2fswE2enokiaE2ecomE2furiE71aX quriE71aZserviceQUxhttpE3aE2fE2fswE2enokiaE2ecomE2furiE71aX qvocZpartOfQUqfnZPublicationQ qwebZserviceQUxhttpE3aE2fE2fswE2enokiaE2ecomE2furiE71aX qrdfZtypeQUqfnZE44istributionQ qrdfZtypeQUqfnZSiteQ qrdfZtypeQUqvocZTermQ qrdfZtypeQUqvocZVocabularyConstructQ qrdfZtypeQUqwebZSiteQ qrdfZtypeQUqrdfsZE52esourceQ qrdfsZisE44efinedByQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fschemasE2fnokiaE2fFNE2d1E2e54E2eowlX qrdfsZlabelQSxForumE20NokiaE20BlogsE20WebE20SiteXLen qrdfsZlabelQSxForumE20NokiaE20BlogsE20WebE20SiteXLen qrdfsZseeAlsoQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fschemasE2fnokiaE2fFNE2d1E2e54E2eowlX