Before you leap into any mobile development you need to identify what
content you want to deliver to task orientated mobile web users. A
mobile site that is simply a repackaged desktop version may be of
little interest to your target mobile user and could warrant
developing mobile-specific content in which case the database
foundation of your desktop site is less of a concern.
I've never been happy with .net mobile as you lose too much control
and their device profiles are terribly out-of-date but I'm sure you
can find plenty of experienced mobile developers on this list willing
to help your company out with its mobile development.
Cheers
Kyle
On Feb 8, 2008, at 11:53, Kapil Sharma wrote:
> I need a kind of suggestion from all the people. Please give me the
> idea.
>
> I have a database driven PC website. The same website we need to
> change for
> mobile handset clients.
>
> I know that the standard for mobile website development have 2
> alternatives
> here in japan
> 1)xHTML (softbank and AU KDDI)
> 2)cHTML (DoCoMo).
>
> or may be WAP .
>
> I just want to know that, Do i need to develop the websites
> differently for
> different phones. How can i check if it will work perfectly.
>
> I heard that google search engine is automatically translating and
> converting websites to the mobile handsets by identifying the kind of
> browser.
>
> Taking into the article as an account
> "ASP.NET Mobile 2.0 to work with the majority of Japanese mobile
> phones in
> the market"
>
> http://decav.com/blogs/andre/archive/2007/06/10/asp-net-mobile-for-japanese-
> phones-docomo-i-mode-softbank-kddi-au.aspx
>
> and
>
> MobileShift AutoConverter
>
>
> Is this the best alternative. Or What is your idea. Please suggest.
Received on Fri Feb 8 08:50:45 2008