Tagged with Architecture
In this eighth part of my series on architecting Windows Phone 7 (WP7) applications, i'll show you how to deal with Toast Push Notifications. If you've missed the past parts of the series, you you can visit them here:
When I say Toast notifications, I am specifically talking about being able to send the phone (e.g. the user) a push notfication that something is important and that the user might possibly want to launch the application. Its a near-time notification to the phone (if connectivity is there). This notification can either alert the application when its running or give the user a notification window at the top of the phone like so:
UPDATED: Added comments on backend story.
I've been knee deep in my book and a super secret project I can't talk about yet but that project and some conversations i've been having (on Twitter and with the Atlanta Pros User Group when we discussed HTML5). It started with the exaggerated death of Silverlight. I was asked at length to comment on what how HTML5 and Silvelright compete and other topics. But after looking at a lot of different things, I came up with a different idea...
In this (somewhat belated) part 6 of my Architecture for the Windows Phone 7, I want to talk about dealing with data across the wire (or lack of wire I guess). If you've missed the past parts of the series, you you can visit them here:
This is at the heart of the idea that the phone is one of those screens in '3 screens and the cloud'. The use-cases for using data are varied including:
Welcome the part 4 of my three-part series on architecting with RIA Services. In the last part of the series, I thought I was done with the example and some of my readers challenged me to help them understand how to handle Add/Delete scenarios. Since I was at it, I figured I should show paging and IsDirty scenarios as well, I decided to make a part four.
I've been looking at RIA Services for a long time now. I had the lucky pleasure of being given early access to the bits for what was then called "Alexandria". As most readers of this blog have read, I have had some issues with how RIA Services works. In the mean time Brad Abrams and the team have certainly responded and have made changes to the way that RIA Services works and much of it is for the better. I can see pretty simply how you can use RIA Services to build applications that are really architected well, with true separation of concerns. But there is blood in the water.
I recently had a chance to look at Brad Abrams' PDC video on Building Amazing Applications with RIA Services and Silverlight 4 (CL21). I am perplexed by some of the decisions on the usage patterns of RIA Services implied by the video. I know that there were other RIA Services talks, but since this was by the head of the team, I think this will be used as the exemplar of what developers should write. And that's unfortunate.
As I wrote and subsequently taught the Silverlight Tour workshop, I've had a number of discussions with students, clients and the community-at-large about how to architect Silverlight applications.
The momentum behind the Model-View-ViewModel (MVVM) design pattern makes a lot of sense to me, especially with declarative views (as seen in Silverlight and WPF). Most of my thinking around this was covered in my MSDN article about it:
Erik Mork (of Sparkling Client Podcast and the Silverlight Tour) has recently done a ten-minute podcast walking through the MVVM example I created for the MSDN article on the subject. He does a great job of distilling the basics and if you are still confused by MVVM, go take a look at the video!
If you are trying to learn what kind of architectures work well in Silverlight applications, take a look at my new MSDN Magazine article. It introduces the Model-View-ViewModel architecture pattern and how it works in Silverlight. You can read the article here: