We are constantly striving to be better and that means we release updated versions to our apps every so often. There are a few important things to be aware of to ensure that users get the best possible experience with your app.
What's a version?
Oomph is a constantly evolving product. We have a development team who work around the clock to make Oomph bigger and better - day in, day out. Their work involves the refinement of existing features, the introduction of new ones and fixes for bugs. When we get to a point where we have a collection of features or refinements that have been thoroughly tested, we release an updated version of Oomph.
Oomph Version Number
In order to make it easy to understand which features are available in each version we use a naming convention of “Oomph Version Number” e.g. Oomph 18. Each major release will result in a new version of Oomph and thus will increase the version number.
Check out what has been added into each version of Oomph here.
How this effects the way you design your content
It's important to be aware of what version your app is running on when designing your content, because your app version will determine the way your content behaves.
For example, our AudioPlayer was released in Oomph Version 21. If a user's app was still on version 18 and a bundle included an audio player, then that feature wouldn't be able to work for that user. To find out what version you're on, follow these instructions.
With each major version release of Oomph, there may be some patches that follow. This normally means that a bug has been discovered that warrants an update to the Oomph platform, but does not result into a new major release. This is where the minor number in the versioning comes into play, i.e. if you see or hear us mention a version number such as Oomph 18.0.1. This means that it is the 18th major release, but it has had a minor bug fix added to it. Generally only effected applications will be updated when this sort of thing occurs.
Why don't we just release new versions of Oomph as features and fixes are completed?
There are a few reasons. Firstly, features and fixes need to pass testing. While our developers are pretty damn clever and spend considerable time working on a feature or a fix, that doesn't always mean the first attempt is going to work perfectly. We won't make anything live until we're completely satisfied with it, as we want to ensure we provide the absolute best user experience possible on the iPad.
The second reason is that if we were to release an update to Oomph every time we updated our source code, we would be on Oomph Version 3,000,000. By the time you submitted your update to Apple and had it approved, we would have released Oomph Version 4,000,000. It's a bit like going to the local shops and needing to go to 6 different stores to get everything you need, or driving the extra 10 minutes to the city where you know you can get it all in the one place.