Microsoft's Smartphone 2003 SDK Released

cd_Csc writes "Microsoft's long awaited Smartphone 2003 SDK was released today. This free download is critical milestone for the Smartphone platform. For the first time, developers are now able to use the .NET Compact Framework to write Smartphone applications using Visual Studio. At Smartphone Thoughts, we have listed the details of what's new in the 2003 SDK along with some screen shots of enhancements to the Inbox and Internet Explorer applications."

Comments

API Reference

[SamBeckett]

bool makeCall(long phoneNumber) - Calls phonenumber. Must be in (xxx)xxx-xxxx format. Returns true on success.

void hangUp() - Hang up the phone. Has no effect if phone is already hung up.

void blueScreen(double p) - Crash the phone with probability p, sampled every 100 cycles, or whenever the user is on phone with his boss. This is determined by the address book.

Re:API Reference

[Anonymous Coward]

you've never seen an API made my microsoft before have you?

that would be

__fastcall bool CMobileDevice::MakeCall (long lPhoneNumber, const CString *StrOptions)

void CCallerObject::PreformHangUp(void *objCaller)


the BSOD is actually a template that they include with every application they develop. Recoding it everytime would take far too much time.. At this time, it's the only known example of succesfull code-reuse in any C++ project outside academia.

Chicken and egg situation

[Peter Cooper]

The XHTML support in these phones is great! As a bit of an XHTML/CSS advocate myself, however, I think browsing the Web from such space-limited devices could become a chicken and egg situation.

A LOT of pages out there are poorly coded FrontPage (or even MS Publisher) not-even-HTML 3.2-compliant junk. There are a lot of amazingly beautiful XHTML/CSS coded pages out there, and they all display well on the small screens.

How many people will buy these phones, surf to their favorite page, and then discover they can't get anywhere fast? Will devices like smartphones and portable computers, with and 3G's ability to access the Internet at speed, force more Web designers to follow the chosen path and design in a fully backwards, and forwards, compatable way with XHTML and CSS? Or will we have a chicken and egg situation where people are turned off from using the devices because the content and pages available to them are so poor.. just like with WAP.

Long awaited

[ultrabot]

Microsoft's long awaited Smartphone 2003 SDK was released today.

Not a slashdot regular, are you?

Really, it is critical that Smartphone not be allowed to succeed. We don't want Microsoft gaining a significant market share there also. If they happen to get something like 20%, they will start "integrating" a lot of proprietary interop stuff to Windows and aggressively wrestle up the marketshare. MSFT Windows/Offics business is winding down, so Smartphones are an excellent migration route because people actually buy new phones all the time.

Symbian is not all that "open", but they have to support public standards, because they have no choice. Do the industry a favor and boycott handsets that run SmartPhone. I don't know how much it is going to help though, because MSFT has endless stash of money to throw to these "strategic" projects. They are not going to drop out even if they sold zero licenses in 10 year.

Obviously multiple platforms means competition, which brings a little bit energy to the market. Smartphones will be a huge thing in a few years, so platform developers can't really be sitting on their asses for long.

Re:DDOS

[ultrabot]

I imagine it won't be too long before someone will figure out how to write a worm to DDOS a companies phone system!

And such a worm would be a boon for operators that charge for calls. Expect the operators' share prices to skyrocket whenever a worm alarm is given :-).

I think the phones should have a hardware "lock" that would require the user to explicitly allow doing an operation that will cost them money.