- Impact
- 223
Did anyone here attend the presentation? Any feedback? I'd really like to hear what went on, and if they took any questions from the attendees.
whitebark said:Sorry mobi fans but like many other metrics on .mobi this one suggests things are not as rosy as some may proclaim. It's been two years and still only .01% market saturation. That's very bad. Anyone who has taken even marketing 101 would know achieving that low of a take-up of a product spells disaster.
If you somehow see roses where I see pure numbers please explain how that can be good for mobi.
whitebark said:Sorry mobi fans but like many other metrics on .mobi this one suggests things are not as rosy as some may proclaim. It's been two years and still only .01% market saturation. That's very bad. Anyone who has taken even marketing 101 would know achieving that low of a take-up of a product spells disaster.
If you somehow see roses where I see pure numbers please explain how that can be good for mobi.
thebiffenator said:I wouldn't say its bad since, its really starting to launch now. I noticed increased traffic every month. Now the hole point of this, is that the traffic is coming from Search Engines
Stats for zem.mobi now averages 400 Unique visitors, 700 visitors and 15,000 hits a month. Now that is with out any advertising at all.
rxd.mobi is a Page Rank 4, and I get emails all the time from large advertsing companies and how they want to work with me. Quatro Wireless, millenium media and more... now I didnt accept because I plan on doing my own marketing campain after 3.0 comes out.
iwantinfo.mobi averages about 20 clicks a day on admob, some days I make $10, thats not bad since its not advertized at all. Most of the traffic is from SEO
I forgot to mention ipad.mobi (that averages 60 visitors a day and 2-3 new signups a day) THis one I advertise about $25 a month through admob and everytime I advertise I get about 3 new users to the dollar. Not bad since, ipad.mobi 3.0 is coming out and I am gona charge money.
NO Need to applogize, I am quite pleased with my results and look forward to a very bright future with .mobi, because my stats only show increases every month. Do you have any stats whitebark to share from your .mobi sites? And I should say the rest can you prove any traffic for developed sites to prove its not alive and kicking? (I am not talking about parked pages) But a fully developed .mobi and where does your traffic come from the most?
GF said:Have you found where your traffic is coming from? Is it all type-in, or are your sites well-optimized?
I'd be happy with stats like those :tu:
HeyNow said:Where did you take "marketing 101?"
HeyNow said:Where did you take "marketing 101?"
miitree said:I did take marketing 101 and those numbers are bad.
IMO: the trend is going towards the .com 's, .net's ... detecting the browser type and returning a page appropriate for the browser. That certainly is the way I'm going. I just completed a a site called www.gpa.me which I designed from scratch with browser sensing in mind. If this site design works out I will be moving that design to my other sites regardless if they are .mobi or any other extension.
sdsinc said:It's not only the SEO cicles that diss mobi... there is no mention of it in cellular industry shows either. Only the speculators care, and many have already shifted focus to the latest extensions like .asia or .me![]()
whitebark said:
Ms. Donna Power said:Some stats about mobile web browsing:
84.8% of the iPhone users and 58.2% of total smart phone users access news and information from the hand-held device.
58.6% of iPhone users and 37% of smart phone users visited a search engine on their phones.
30.9% of iPhone users have tuned into mobile TV or a video clip from their phone.
74.1% of iPhone users and 27.9% of smart phone users listen to music on their mobile devices (Source: mMetrics)
Nielsen mobile recently proclaimed that the mobile internet had reached “critical mass” w/ more than 40 million users today.
Ms. Donna Pawar said:Why is .mobi less than ideal?
Bad for SEO (Mobile and Traditional)
Splits traffic, you have to duplicate effort.
Splits links
Splits Index size
Doesn’t benefit from history
Risks Duplicate content
Confusing for Users
There's no preferrence for it in Mobile search engines
No unique assets or features
Best Practices
[...]
Set up a subdomain just for mobile – something like m.domain.com; wap.domain.com, etc. and then duplicate your existing site on the subdomain, but tweaked specifically for the smaller format of handheld devices.
Advantages to this method? Just update your existing code. Adjust the level of content so it’s easier to read on small screens/on the go.
I can say that .com is actually declining 5% each year since 2000 when it comes to the quality of websites, but that means nothing until I actually give a source or reference as to how this was determined. Likewise, I'd like to request how the 0.01% was derived for .mobi websites.Less than 0.01% of SMBs have invested in a .mobi website.
Excellent post!! It's weird how some people ignore the obvious. With subdomains, to many variations come into play. Thus, the consumer is left guessing every time they access internet via mobile. Now with mobi, it's all good. Easy to remember and the content is readily available every time!DBADT2007 said:I'd like to thank whitebark for providing this link.
Don't you just love how Ms. Donna Pawar misrepresents the data she is providing? I know I do; its just makes it that much easier to disprove her arguments.
Why don't we take a look at the numbers she provided...
If you are a savvy business person you can just see through Ms. Donna Pawar's bag of smoke 'n' mirrors. And for one thing, I'm not buying. One of things that .mobi investors have been called from the naysayer camp, is having rosy colored glasses, but its actually the naysayers that are kidding themselves when they use Ms. Pawar's statistics as facts.
I'll take a moment to analyze her statistics...
1) All references are in terms of the iPhone or smart phones. This in itself is misleading, since the entire global market is not made up of iPhone/Smart phones. In fact, according to AdMob Mobile Metrics, iPhones + Smart Phones make up less than 5% of the global market share as of July 2008 data. Therefore, if I put this into perspective in correlation with her percentages, the numbers are not nearly as large as she tries to imply.
Only 4.24% of the entire global mobile market (percentage of iPhone marketshare) and 2.91% of the entire global mobile market (percentage of smart phone marketshare) access news and information from their hand-held device.
2.93% of the entire global mobile market (percentage of iPhone marketshare) and 1.85% of the entire global mobile market (percentage of smart phone marketshare) visited a search engine on their phones.*
1.55% of the entire global mobile market (percentage of iPhone marketshare) have tuned into mobile TV or a video clip from their phone.*
3.71% of the entire global mobile market (percentage of iPhone marketshare) and 1.40% of the entire global mobile market (percentage of smart phone marketshare) listen to music on their mobile devices.*
*Of course there are generalizations that can be made for most mobile phones; when it comes to accessing information, search engines, etc. However, this data does not accurately portray the global mobile market. Therefore, to present data as if the entire world was made up of iPhone/SmartPhones is seriously flawed and that is what I am portraying by adjusting percentages to show the iPhone/Smartphone marketshare in comparison to the global market.
2)
Nielsen mobile recently proclaimed that the mobile internet had reached “critical mass” w/ more than 40 million users today.
Now, she then follows to misrepresent what the Nielsen mobile statistics are saying. Since, the Nielsen mobile statistics seem to imply that it includes all mobile phones, and not just iPhones/Smart Phones. However, Nielsen Mobile does not provide sufficient data to ascertain what actual percentage of these 40 million is really iPhone/Smart Phone users. Therefore, the reference is flawed. I for one can vouch to be constantly on my phone using my internet access and have an unlimited data plan with my mobile service provider and its not an iPhone/SmartPhone, per se, therefore to assume that the entire base is made up of iPhone/SmartPhones is certainly flawed.
Another interesting point she brings up...
So she states that .mobi is less than ideal, because of duplication, yet she suggests doing just that later on for a subdomain. Is it just me, or did Ms. Pawar just contradict her own message? And if I do follow with adapting the content to be optimized for mobile devices by duplicating on a subdomain (which subdomain will I use? Will the mobile user magically know and remember which variation I chose for my mobilized version? Either m.company.com, mobile.company.com, wap.company.com, oh wait I think its company.com/mobi, or what was it?).
And if it seemed to you like you just created an entire mobile site, which could have been easily been placed in a .mobi domain, well you are correct. The only glitch would be that by using Ms. Pawar's suggestion I just lost who knows how many mobile users that would have remembered and recognized my site had I made it a .mobi website, just pure in simple, company.mobi. Imagine that, it couldn't had been simpler. Yet I chose to use some kind of subdomain, which the user can't remember or may confuse with another company's mobilized version (e.g. wait was it live.com/mobi or was it cnn.com that used the '/mobi' - I can't recall), thus they just didn't visit my mobilized site at all.
Now, if you think auto-detect is the answer, think again. I know I would hate to be forced to access a full blown website, when I wanted to access a mobilized version of it. Why is it so hard for webmasters/seo to see this? I still remember the fixed vs fluidic argument when it came to creating websites, why oh why would you want to create an auto-detect code that sets a fixed full-blown website, if on an iPhone/SmartPhone, when in fact its not what the user may want.
Atleast when it came to the CSS; I felt that Ms. Pawar had at least tried it before actually making assumptions that it would work on all phones, so kudos to her for doing at least a bit of research when it comes to CSS implementation.
Dynamic mobile sites. Now that is an idea! Imagine how much of a drain it will be on your servers when your site becomes popular enough that it actually is getting millions of hits or when its under a DOS attack by a hacker. In fact, some hosting packages have restrictions when it comes to having scripts running continuously. And if you are not careful you may be terminated by your host provider.
Now, I really would like to know where MS. Pawar got her stats from:
I can say that .com is actually declining 5% each year since 2000 when it comes to the quality of websites, but that means nothing until I actually give a source or reference as to how this was determined. Likewise, I'd like to request how the 0.01% was derived for .mobi websites.
So now I leave you all to ponder "Ms. Donna Pawar's Truth" vs Reality.![]()
thebiffenator said:Will it be M.site.com or M.site.net or site.com/mobile or site.net/mobile or wap.site.com/com/net/asia or will it have a browser sensingcapability? If it does have browser site capability, how will it act with standard small screen ?at the same time what about the iPhone? Will the site be catered for brief periods of searches and to view quick sites to get the info?
Auto detection is great for the sites that use it. The problem is, all don't. And until that unlikely scenario comes into play, there will always be doubt in a mobile surfers mind. Nothing quite like visiting a full blown site that takes forever to load and either shuts down my browser or doesn't display. That's where mobi steps in to promise ones visit will be mobile friendly.miitree said:Thank you for commenting on my site. I don't know if this is the way it should be done but the way I handle the dynamic detection is by simply using the same url for all users. All responses are generated dynamically. I have 3 types of responses. Full web browser, iphone, and other mobile. I use a very simplified test on user agent to determine which of the 3 types to use for this request. Then the response if formatted accordingly. So the URL is always the same.
The subroutine for browser detection follows...
------------------------------------------
sub check_browser
{
$mobile = "";
if ( $ENV{HTTP_USER_AGENT} =~ /iPhone/ ) {$mobile = "iphone";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /iPod/ ) {$mobile = "iphone";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /Android/ ) {$mobile = "iphone";}
elsif ($ENV{'HTTP_REFERER'} =~ /testiphone/){$mobile = "iphone";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /Windows CE/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /BlackBerry/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /AvantGo/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /DoCoMo/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /Vodafone/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /WM5 PIE/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /Opera Mini/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /MOT\-/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /LGE/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /Nokia/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /Palm/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /SAMSUNG/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /SonyEricsson/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /PLAYSTATION/ ) {$mobile = "y";}
elsif ( $ENV{HTTP_USER_AGENT} =~ /SymbianOS/ ) {$mobile = "y";}
elsif ($ENV{'HTTP_X_WAP_PROFILE'} ne "") {$mobile = "y";}
else {}
return;
}
-------------------------------------------------------
I think this covers over 90% of the smart phone target audience. I didn't want to use the huge databases which map user agents because I think they would put too much load on the server. Search engine indexing at times can get very high. I have seen requests at a rate of about 3 per second continuous 24 hours a day. So rapid response is important to me.
Also, I have many .mobi websites. The most successful are www.iteams.mobi and www.ischools.mobi. So believe me I do want .mobi to succeed. It is just that revenue wise the sites don't generate much when displayed on a mobile device. But they do get good revenue when accessed from full browsers (I would estimate over 95% of the total revenue). Once again the sites use dynamic browser detection.
Overall the .mobi experience for me has been positive in that it got me thinking about mobile devices. However, I think the future is for the more conventional domains (.com, .me) using browser sensing and returning a page accordingly. USAToday and CNN are good examples of this.
Again thanks for commenting on my site.
:D :D :Dkeithmt said:It's weird how some people ignore the obvious.
Work In Progress said:Auto detection is great for the sites that use it. The problem is, all don't. And until that unlikely scenario comes into play, there will always be doubt in a mobile surfers mind. Nothing quite like visiting a full blown site that takes forever to load and either shuts down my browser or doesn't display. That's where mobi steps in to promise ones visit will be mobile friendly.
As for your non-mobi sites (such as GPS)...how will surfers know it's mobile friendly? Are they supposed to guess or cross their fingers? I'm willing to bet few non-domainers out there have heard of .me...I'm not saying mobi is either...but it's got quite a jump on .me....The only way I can see is by you spending loads of cash to promote it as such. I'm not trying to disrespect you in any way. Just trying to see your logic.![]()
miitree said:However, I think the future is for the more conventional domains (.com, .me)
namewaiter said:for the most part i agree with your post, but .me huh???
also, the iphone still has very little overall penetration %, i'd watch building out specifically and only for it.
but good luck with your sites, own iteam.mobi and it might explain where some of the traffic comes from.
miitree said:I have seen requests at a rate of about 3 per second continuous 24 hours a day. So rapid response is important to me.
mwzd said::D :D :D
The truth will set you free...
Everyone knows I'm a naysayer... so I'll let it rest.
DBADT2007 said:Hi Dbad...
So that comes to about 259,200 requests per day or 7,776,000 requests per 30 days. Have you experienced any downtime on your servers due to this load? How much memory on your servers does the script actually need to process and how does multiple requests effect your website response? Do you have dedicated servers for this site? And how will greater content (as students start to develop their websites) affect your servers? What if most content is images, videos, etc. How will you handle this?
From further research, I noticed that your site still has no rank in both Google or Alexa, however to me this is understandable since .me is fairly new to the domain address game. Upon further searching I also found that Google has accessed multiple links from your site, but has yet to find much content. Once again, quite understandable since you are still getting the word out.
The questions I'm asking is not to discredit your website- I am legitimately interested in these questions, because I know that auto-detection can be a great utility but it can also cause major pains as your site becomes popular and well visited. Which is why I question the effectiveness of auto-detection as an end-solution.


