So what's the problem? Well when a user reinstalls your app they have to start from scratch, any settings/customisations they make to your app are lost and this barrier to re-entry can sometimes force users to simply go elsewhere. In an ideal world a user should be presented with the option to restore their settings/customisations to you app when they load it for the first time after the uninstall/on the new device. Obviously any settings stored in Isolated Storage are lost so if you want to provide this experience you will need to save these settings in the cloud.
]]>Often on the marketplace I have seen apps that have multiple reviews by different users just saying things like "Crashes on startup!" or "Doesn't work on my device!", and as a developer I know its frustrating to see things like this when the app is working perfectly fine on your phone. While it would be nice for users to provide detailed repro' steps and associated data, that's not really likely to happen, but in my opinion the main thing you want as a developer is the Exception and a Call Stack of whatever is causing the app to crash.
]]>Anyone who has had a bad experience with your application is motivated to go and leave it a scathing review, where as the hundreds of people who loved your app may never even consider leaving it a good review. One way to counter this is to simply ask those users who like your app to leave you a review, however you don't want to bug people too often or before they've had a real chance to use your application. So what can you do?
]]>Adding a trial mode to an existing paid application is very easy to do and highly recommended, even if you also have a 'free' version of you app available on the marketplace, because it lowers the hurdle between a user seeing your application and a user making the purchase. Also improvements to the on phone Marketplace rumoured to be coming with the release of Mango this Fall will mean that paid applications with trials are highlighted more than those without.
]]>Hopefully this is some sort of confirmation that Turn-by-Turn directions will indeed be coming to the UK when Mango ships later this year!
]]>There were 2 main places where I found information on how to potentially write you own Binary Serializer for WP7, the first I felt took a rather old school approach by adding a "Write" function to each class which accepted a BinaryWriter and simply wrote out each of its own properties. The clear problem with this approach is the maintenance involved with adding new properties or if you wanted to serialize a different class.
The second approach was explained by Eugene Chaikin on his site, where he attempted to replicate the DataContractSerializer's interface and even make use of the '[DataMember]' attributes in the same way.
]]>
1: // Save
2: MyClass theData = new MyClass();
3: using (IsolatedStorageFileStream fs = isoStore.OpenFile("MyClass.xml", FileMode.Create))
4: {
5: DataContractSerializer ser = new DataContractSerializer(typeof(MyClass));
6: ser.WriteObject(fs, theData);
7: }
8:
9: // Load
10: using (IsolatedStorageFileStream fs = isoStore.OpenFile("MyClass.xml", FileMode.Open))
11: {
12: DataContractSerializer ser = new DataContractSerializer(typeof(MyClass));
13: MyClass result = (MyClass)ser.ReadObject(fs);
14: }
This is all well and good for getting something up and running quickly, but once you start having more complex classes and/or more data, performance starts to become an issue. A quick test of how long AppTracker currently takes to deserialize the cache file when following just 3 apps (Polyglot, Gifts and AppTracker - consisting of a total of about 544 reviews) resulted in the following timings:
]]>