Home/ Questions/Q 848627
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T06:58:26+00:00

I am developing a Windows Phone app where users can update a list. Each

  • 0

I am developing a Windows Phone app where users can update a list. Each update, delete, add etc need to be stored in a database that sits behind a web service. As well as ensuring all the operations made on the phone end up in the cloud, I need to make sure the app is really responsive and the user doesn’t feel any lag time whatsoever.

What’s the best design to use here? Each check box change, each text box edit fires a new thread to contact the web service? Locally store a list of things that need to be updated then send to the server in batch every so often (what about the back button)? Am I missing another even easier implementation?

Thanks in advance,

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Data updates to your web service are going to take some time to execute, so in terms of providing the very best responsiveness to the user your best approach would be to fire these off on a background thread.

    If updates not taking place (until your app resumes) due to a back press is a concern for your app then you can increase the frequency of sending these updates off.

    Storing data locally would be a good idea following each change to make sure nothing is lost since you don’t know if your app will get interrupted such as by a phone call.

    You are able to intercept the back button which would allow you to handle notifying the user of pending updates being processed or requesting confirmation to defer transmission (say in the case of poor performing network location). Perhaps a visual queue in your UI would be helpful to indicate pending requests in your storage queue.

    You may want to give some thought to the overall frequency of data updates in a typical usage scenario for your application and how intensely this would utilise the network connection. Depending on this you may want to balance frequency of updates with potential power consumption.

    This may guide you on whether to fire updates off of field level changes, a timer when the queue isn’t empty, and/or manipulating a different row of data among other possibilities.

    General efficiency guidance with mobile network communications is to have larger and less frequent transmissions rather than a “chatty” or frequent transmissions pattern, however this is up to you to decide what is most applicable for your application.

    • 0