Automatic Updates

[benering]

I would like to see automatic updates added to the functionality.

[tomasq]

I think Xobni already performs automatic updates. What I would actually like to see is the ability to control whether or not Xobni checks for updates.

[bryan]

That's true. Xobni Insight checks for updates automatically.

If your client is not updating, please contact support by clicking on the Xobni menu in outlook and selecting Contact Support.

tomasq: This is good feedback. What would make you want to disable automatic updates? Or do you mean having a "force" update feature?

[tomasq]

tomasq: This is good feedback. What would make you want to disable automatic updates? Or do you mean having a "force" update feature?

Both a "force" update feature and a disable feature.

For the disable automatic updates, there are numerous cases in which application updates are released only to be updated again (this is true in the open and closed source worlds). I am the type of user that likes to be notified of an update being made available, letting it sit for a week, and then applying it.

Additionally, in my corporate environment, I would not want users mass updating at the discretion of a product manufacturer.

I believe in the early beta stages of your launch, automatic updating without user intervention is acceptable, however as your product matures and moves out of it's beta stages, it may be wise to allow users to have control of their update frequency.

A "force" update feature would be a positive offering, in instances where users are having troubles updating their client for one reason or another, as I have seen in other threads.

Lastly, updates being made available via notification and the user being in control of applying the update allows the user base to see the development process evolve. By your current model, if a feature is released with an update and breaks functionality, the user base will not know whether or not this is due to a version change. By allowing the user to select whether or not they wish to update, they will know a version change has occurred. That knowledge is crucial to diagnosing troubles, in my opinion at least.

Sorry for being wordy, and for hi-jacking this thread!

[adamsmith]

All good points, tomasq. We will probably work such controls into the workflow as the product matures and gets ready for large deployments.