I typically scan well over 250 feeds a day! Yep that's right I'm an addict - actually I don't normally get beyond the Perth Bloggers network (which I have as the feed in [VS2005]) and most of the Australia Microsoft DPE team. Anyhow today I was glad that I spent the time scanning for interesting content because I came across this great little post by Anna Liu which points to a video on YouTube that shows an innovative user interface for the next generation of mobile devices.
Unlike the disappointing attempt of Deepfish to provide a usable experience for pocket pc devices this interface seems like it has actually been tailored for these devices. I had to laugh though because in 2004 at the Imagine Cup finals in Brazil we saw an interface that would make these guys drool. The concept behind the application itself was to provide a guide for people walking around a museum but the menu system these guys had come up with was second to none. They had worked on the spin out menu concept where you start with a minimal dial in the middle of the screen, select an item which then spins out a new dial. As you progressively select items new dials appear; if you want to go up a level you click the centre. These guys had made it entirely customisable and the menu itself was all images (rather than simple text) so it looked unbelievable. I just wish I could get in contact with these guys!
For almost as long as I've been working with .NET I have been an advocate for building rich client applications (aka smart client applications) that work in an occasionally connected manner - think Outlook cached mode. Recently there have been a couple of posts such as "You're not on a f^&king plane (and if you are, it doesn't matter)!" and "The Mile High Club: 37signals, f@#k yeahs, and productivity stock-art" that talk about the current trend of people talking about providing caching/offline capabilities to their web applications. IMHO they all miss the point. Building web applications that will work offline is NOT the solution - you need to build rich client applications that are DESGINED to work offline.
Ok, so let me explain: The basic premise of building occasionally connected applications is that you work on the assumption that the application WILL be offline. To enable this you work with a local datastore (assuming a real world application that works with some sort of data) and you build an rich application that doesn't require any network access. You then need to consider how the data is going to be synchronised to the local datastore (again, assuming a real world application where you want the data to be kept in a central repository). This can be done using technologies such as Merge Replication, RDA, MS Sync Services but essentially this is a separate concern to building the application itself.
So, why is this better than just coding an application that will continue to work when I pull the network cable out? Well it all comes down to usability - according to Microsoft we are in the Age of User Experience (which IMHO is rubbish, just because Microsoft has entered the design application market does NOT mean that we have only just started to think about usability - more on that later). Usability of web applications has a fundamental problem in that it relies on request-response model back to the web server. Even with the best implementation of Ajax you are still likely to experience delays, refreshes etc that lead to a poor user experience. On the converse a rich client application "should" have smooth usability with no wait times between screens. I know which one I would prefer!
Finally, back to my point about the Age of User Experience; Despite two iterations of the .NET Framework WinForms essentially hasn't changed since the old C/VB days. A lot of companies have invested heavily on extending forms and controls to make their applications look good. Of course there were always challenges making the application responsive - you could introduce multiple threads to load data, but then you ended up debugging locking issues etc.
Now with the Windows Presentation Foundation we have a much rich (or so they keep claiming) framework with which to build applications. I must admit the applications I have seen to date have all looked great, but they nearly all diverge from using standard menus or having a familiar look and feel - tell me how this is suppose to empower users?
Whilst WPF is a significant improvement when it comes to building rich client applications there is still a long way to go before "usable" and "applications" become synonymous!
In my previous post I wasn't that positive about the new mobile browser, Deepfish, that Microsoft Research have been working on. This morning I decided to give it another shot, this time on the i-mate SPL device. The first problem I encountered was that you can't install both the Pocket PC and Smartphone versions on the same desktop. I suspect (hope) as this product reaches RTM this will be resolved into a single download and installer.
Once installed I was literally amazed with how easy Deepfish is to use. To give you an idea I thought that I would grab Pocket Controller and take some screenshots. BTW this is the first time I've really used Pocket Controller (Dave Glover swears by this product) and the whole experience has been great -> Installation, Connection and working with the device.
Integration into Programs (an improvement over the PocketPC version)
Website in fullscreen
Pressing Enter displays the Zoom selector which can be controlled using the cursor pad -> very intuitive, unlike the Pocket PC equivalent
After zooming - The Cuemap shows where on the page you are. Again the cursor pad can be used to navigate around the screen.
Pressing Enter again turns on navigation mode - links are highlighted and a small arrow appears over the link. Again the cursor pad allows you to roam through links in the current view (pressing Back goes back to scrolling mode)
This sounds like I'm trying to start a food-fight. In fact, courtesy of Steve, Development Manager here at [Intilecta], I thought I'd share an interesting article that talks about the Language V's Tool divide (Full article available here). Just as an aside, the author of this article seems to be involved with the OpenLaszlo project which strikes me as "just another web technology" (it might ease the pain of doing web development but it won't make it go away....)
Ok, so back onto the topic of this post - the article points out that if you have $100 to spend on improving a language you have to choose between spending money on improving the language itself (thus increasing the power and efficiency with which developers can write code) or tool support (which can also improve the efficiency of the developer). Try as you might you are not a magician and you can't make $100 into $200 and thus be able to do both.
Now apply this logic to the C# v's VB.NET debate and the decisions the teams make about priorities. Clearly with C#'s background in C, C++, Java and other languages there has always been a strong focus here on extending the language. That said, with [VS2005] C# made considerable improvements around intellisense and refactoring.
On the converse VB.NET has always been the leader when it comes to tool support for the language. Whilst the language did get most of the features of C# (such as generics, nullable types etc) there were a few things which were left out -> iterators and anonymous methods to name just two. So where did the VB.NET team spend their $100 - the My Namespace? Agreed My does provide significant savings when it comes to doing common task but I must admit I was sorely disappointed that the VB.NET team decided not to give us feature parity w.r.t. the language. Further more our complaints seem to be going unnoticed with iterators and anonymous methods still missing the cut for the Orcas release.
The argument keeps coming out from Microsoft that they need to differentiate the two languages to justify the cost of maintaining two languages, compilers etc. Quite frankly I think this is a silly response and that if this is their primary concern, then they should just get on with it and axe one of the languages. This would not only free up resources to be more innovative it would also stop this continual need for developers wasting valuable resources deciding which language to code in (after all if we only had feature parity there would be no discussion....)
While I was in the UK last month I decided to find a replacement phone for Meg, who has been using a Smartphone 2 for the last couple of years. After much consideration of all the new devices on the market I decided to go for the i-mate SPL. At the moment this runs Windows Mobile 5 but I'm hoping that since it is such a recent phone (like it hasn't even been released here in Australia yet) that we might see an upgrade path to Windows Mobile 6. Regardless, I don't think not having an upgrade will really phase Meg.
Anyhow after a week or so of tracking the package using the Expansys and DHL websites it eventually arrived today. My first impressions are that it is a slim and lightweight as I was hoping. Here are just a few screenshots:
The i-mate SPL Top and Bottom
Screen and Camera
USB port (open) and Wriststrap connection point
USB port (closed) with Photo Button, and Sound Controls
Microphone (in the base) and the Sound Controls
Now we're talking - Inside and the SIM tray
Other than taking me a while to work out how to turn the keylock on (which by the way you can do by holding down the home button) my first couple of hours with this device have been a real pleasure. I must admit I'm not really a Smartphone kinda guy but I might consider using this device for a short while (at least until my K-Jam comes back from its road trip to the US).
I've started trawling the web for any information I can get about the next version of Visual Studio. As you can guess, it's about time for me to start considering the next version of [VS2005] (clearly with a bit of a name change!). Anyhow here are a couple of posts I just came across the outline some of the new features:
- Team Foundation Server (TFS) Roadmap
- Occasionally Connected Systems Designer
- Visual Studio Team System Roadmap
- Visual Studio Orcas Overview
- Visual Studio Orcas Features List (not a full list I might add looking at the features for device developers versus what is already available in the March CTP)
I just noticed that you can download the Alpha (interestingly they use that instead of the usual "Community Tech Preview") release of the Windows Live Id Client 1.0 SDK. This comes with documentation and a simple application that demonstrates authenticating using your Live credentials. Scott's got a great article on getting started with the SDK.
Across on the forum there have already been questions raised about whether this can be used to authentication for websites and on mobile devices. My burning question is whether they have planned to support occasionally connected applications? What happens when my connection fails - does it log off immediately? do I need to log in again? Can I logon when I'm offline (assuming I've previous logged on using this computer in the same way as the operating system)?
Last week there was quite a bit of hype around a new browser concept coming out of Microsoft Research, Deepfish. I was luck enough to be included in the beta so I thought I'd share some comments.
Before we look at Deepfish I thought I'd test out Windows Mobile 6 to see what the [Intilecta] website looks like. One area where Microsoft have made signficant improvements with WM6 is with the web browser - this is clearly evident if you take a look at the following screen shot:
Next we look at Deepfish: As with most other mobile applications you install Deepfish on the desktop, then the next time you connect your device it will be installed via ActiveSync/WMDC. The following screen shots are how the website looks after navigating to the website using Deepfish.
Deepfish - Initial page load, Zoom square, Zoomed in with Cuemap
The initial screen shows the website rendered as it would be on the desktop. Despite being quite small it is easy to determine where everything is and get an appreciation of what part of the site you want to read. In order to read the text you need to zoom in - clearly this part of Deepfish has been designed for the smartphone as it SUX for the pocket pc. To zoom in you press the Enter key, then use the stylus/direction pad to move the zoom square around. IMHO I think this would be much better if you could use the stylus to select a rectangular region on the screen to zoom in on.
Once zoomed in, the experience for the pocket pc user isn't much better. An ideal experience would be for the user to be able to drag the stylus around the cuemap and for the screen to follow - instead you have to select a new spot on the map and then the screen moves there; similar but not the same.
First impressions: great start, but a long long long way to go!
As most software developers understand moving from v1 of a product to v2 causes all manner of grief. In particular it is usually the first time that you think about how you are going to version your product. I don't mean just giving it a version, I mean how you are going to upgrade v1 users, how you are going to increment version numbers etc.
I was talking to Bill last week about v2 of the Device Emulator. This was originally incorporated into Visual Studio as part of the extensions for device developers but since [VS2005] it has been available as a standalone emulator that can be used for demos, testing etc. Bill wanted to know whether installing the standalone version overwrote the version which gets deployed with Visual Studio. For the record the answer is yes it does but this is definitely not evident from looking at the file system:
- Firstly, to ensure that v2 does infact replace the version that Visual Studio launches it is installed into the same location on the file system (namely: C:\Program Files\Microsoft Device Emulator\1.0)
- The file version (which is also the version reported in the About dialog) is 8.0.60801.0
Clearly there wasn't much thinking about versioning when the team were planning this one?
Alex pinged me a week or so back asking me to spread the word about the Architecture Camp that the NZ community is running. I must confess that I completely forgot and it wasn't until I saw this post that I remembered. Anyhow, for anyone interested in talking
shop architecture for a weekend, in a similar style to Code Camp Oz, you might want to start planning now!
Normally I wait until I can get a copy off the back of a truck before I both playing with a new piece of software but in this case I've been so eager I figure I'd bite the bullet and purchase a license to the new [OpenNETCF] Smart Device Framework v2.1 (with [VS2005] Extensions). The other reason I felt I should make this purchase is that it is only $50 (single license) and that I figure it would help these guys continue their great work.
Although I haven't really got down to playing with the various controls and classes I am suitably impressed with the level of integration and the setup process they have. Here are just a few shots of me "opening the box".
Installer package even has the correct icon
The installation process
Integration into Splash Screen
New Project types
New Controls, already added to the Toolbox
Check out the list of contributors
Appropriate listing in the Start Menu
Neil has just announced that version 2.1 of the [OpenNETCF] Smart Device Framework has just been released. Although they now charge for this framework it is no longer just a class library that gives you missing desktop functionality. With tight integration into Visual Studio 2005 this framework is essential for all windows mobile developers.
Once I start playing with the new version I will endeavour to post about some of the new features I come across.
On Friday I heard an unconfirmed rumor that wireless was soon to be made free in the Qantas Club. This morning I thought I'd put it to the test and sure enough: It's Free. You still need to connect via the Telstra redirect site, but that's as simple as clicking the button.
All I can say is - About Time! Now all we need to do is convince the hotels that charging $20+ a day is just extortion.
I was just reading a post by Steve Lasker in which he describes how you can create a SQL Server Compact Edition database and how you can detect if the database already exists. One of my complaints about the introduced "|DataDirectory|" substitution is that it isn't understood by System.IO. Luckily it doesn't need to as the .Database property on the SqlCEConnection object returns the path to the database with the appropriate substitution made:
My.Settings.LocalConnectionString:= Data Source ="|DataDirectory|\Another.sdf"; Password ="SomePassword";
Dim localConnection As New SqlCeConnection(My.Settings.LocalConnectionString)
If Not System.IO.File.Exists(localConnection.Database) ...
Having unsuccessfully attempted to image my device to WM6 I thought I'd check with i-mate to see if they had plans to release a WM6 ROM for this device:
Jose> Welcome to club i-mate support. My name is Jose, how can I help you today?
Nick> Hey Jose - quick question regarding the k-jam
Nick> given this device is a little over a year old I was wondering whether there is going to be a WM6 ROM made available for this device?
Jose> yes there is going to be upgrade
Jose> but there is no date of release
Looks like there will be a ROM out for the K-Jam (aka Wizard) but no idea on the timings.
This weekend has been full of lots of action and adventure. After negotiating the Melbourne traffic on Friday afternoon I managed to pick up Phil and make the drive out to Wagga Wagga (only got slightly lost around Albury). One of the best parts of Code Camp is the first evening when everyone has just arrived and ends up at the same restaurant. Although it took about an hours to get any food it is the perfect opportunity to catch up with what everyone has been doing.
I came to the conclusion that the world is all too small. Two members of the French team that won the 2004 Imagine Cup, Aymeric Gaurat Apelli and Francois Beaussier, now work for Readify. I remember these guys as their level of innovation set them apart in a competition where every single entry would put most commercial organisations to shame. It's great to see that an Australian company is recruiting some of the best up and coming international talent!
Unfortunately I wasn't able to stay for the entire camp but I was their long enough to see Damian and Paul give their Ajax session, to give my session on Synchronisation (hopefully audio (from the Perth user group) and the slides will be available later this week) and to see Grant's (who is now an MVP) session on TFS.
Here are just a few shots of Code Camp 2007 (taken with my K-Jam before I flashed it to
WM6 WM5 - turns out the image was only WM5 - Doh!):
Fellow Perthite, Stephen Price (I think that's me in that photo!), made the journey too!
Damian looks on while Paul shows how to use an Updater Panel.
Mitch gets a shot with his JasJar while his Tablet PC sits idle.
Following another 4.5 hour drive back to Melbourne on Saturday afternoon Meg and I went out to watch the George Coleman, Jr Quartet at Bennett's Lane Jazz Club. Truly awesome and I'm so looking forward to the Herbie Hancock concert in Perth later this month.
Yesterday afternoon Meg and I went to the final session of the FINA World Championships to watch the Waterpolo. This was held at the Melbourne Aquatic centre and they had setup more security than most international airports. We thought they were going to confiscate the coffee we were taking in, but it became apparent that they were looking for more dangerous articles. When the bronze game got started we knew we were in for an entertaining afternoon as Serbia were playing Spain. While I have a lot of respect for all nations competing, the Serbian fans are nothing short of thugs. They are the only nation that frequently booed the opposition - talk about poor sportsmanship!
The other interesting thing was that they had setup these flamethrowers (careful Sandi, don't get too excited) at either end of the pool that would go off whenever a goal was scored. Even back in the stands you could feel the heat that these things gave off.
For some reason this week seemed to disappear. After getting back from my trip around the globe last weekend I was excited to launch back into work. Dave and I are now working out of the Perth Annex - the Perth extension to the R & D Centre for [Intilecta] based in Wellington. Part of my time while I was in NZ was to help with the transition from SourceSafe to Subversion. This was only one part of a much larger initiative to upgrade our internal infrastructure. Already we have noticed a massive improvement in our ability to work remotely.
This leads me to my next point which is that I'm again on the road, this time at the Qantas Club in Melbourne on the way to Code Camp Oz. This is definitely one of the developer highlights of the year, although being in Wagga Wagga it is a pain to get to for people who don't live on the East Coast - not only do we have to fly to the East (Sydney, Canberra or Melbourne), we then need to organise transport to Wagga, not to mention the additional days leave in order to get to and from the event. For future, guys (Mitch and Greg) I think it is time to rethink this decision and move it to a more hospitable location. This would also encourage international developers, such as Alex, to come across.
Yesterday morning didn't start out particularly well for me. If you have ever played around with adding/removing mail accounts from Outlook you will probably know that if you remove your Exchange mail account it removes your primary mailbox (ie the OST file). Normally this isn't a problem because you can setup your mail accounts, reconnect to the exchange server and sync your mailbox. Unfortunately the reason I was playing around was because the SoftTeq mail server had died so I couldn't reconnect. Luckily I was able to download a OST to PST application that did the trick.
The real reason for this post is that I then went looking for an alternative to us managing our own server (basically we were only using the exchange portion of SBS anyhow as SoftTeq is no longer a commercial venture). This is when I came across ExchangeMailHosting, which is actually run by IT Solutions Now. I was looking for a hosted exchange solution that was relatively cheap, that used Exchange 2007 and supported RPC over HTTP (so I could sync on the run and from my mobile device). For $9.95 per mailbox per month this service is quite good value.
It gets better - if you want a baseline to compare service against then these guys are quite high up there. I filled in their online application form and within an hour I had an email saying that the service was up and running. Within 2 hours I had setup Outlook (as per instructions in the welcome email), I had accessed their web access site and I had sync'd to my mobile device. When their application form said that someone would contact us within 24 hours I'd assumed I'd get a phone call at 3am to complete the process - but instead "It All Just Works"!
Lastly I want to point out a great new feature in Exchange 2007: After Windows Mobile 5 was released there was a service pack for Exchange 2003 which allowed an administrator to remote wipe a device that was syncing with the Exchange server. Clearly this was a little inefficient since it requires an admin to get involved at 3am when a drunk employee realises they left their phone in the Taxi. The new and improved Outlook Web Access in Exchange 2007 has the ability for the user to Self-Serve through the Options -> Mobile Devices screen, as shown in the following image.
The author of sync-mobile has added another post that discusses scheduling strategies for synchronisation of data. In this post they outline three strategies for scheduling or kicking off a sync:
- SMS - There is definitely a risk that messages can be delayed or might never reach the target but on most networks this latency/risk is pretty low. In fact in NZ they use SMS as a mechanism for paying for parking - the latency is 5-10 seconds which is usually adequate for most scenarios. Don't forget that Windows Mobile 5+ now has the notification engine means that you can write managed code using the .NST Compacty Framework to intercept SMS messages, even if you application isn't running!
- HTTP/TCPIP - Their main point with this strategy is that battery life is a premium which I would have to agree with. There is also the additional cost of network traffic (for those countries like Australia/NZ where data is still expensive). This said, since the release of the Security and Messaging Feature Pack for Windows Mobile 5 we have had Direct Push email - this basically establishes a connection to the Exchange server that remains open even when the device goes into standby. There is a great article on MSDN that discusses how you can use this technique in your application. In my experience the drain on battery power is actually not that bad using this technique.
- Scheduled Sync - Ok, now we are talking - this is a technique I have used a couple of times. The biggest issue here is that in managed code any sort of timer you use has the issue that it won't be triggered if your device has gone into standby (which it is likely to do in order to extend battery life). This is where you really need the power of the Smart Device Framework from the guys at OpenNETCF so you can use the Large Interval Timer in order to wake your application up.
It would be great to hear what other techniques people use in order to trigger synchronisations - do you monitor network availability, sync on application startup/usage or do you have other business rules that drive when you synchronise. Do you detect what type of network you are connected to and determine whether you should sync based on the cost of the network (see the Mobile Client Software Factory - Disconnected Service Agent and Connection Monitor blocks for quite a nice implementation of this)