[e1ven]

I don't think they pulled it to force people to upgrade.. I suspect they pulled it because selling multiple versions would be confusing.

It's clearer if there is one app per platform. Getting my wife to use a password manager is tough enough - Having to explain why there are 14 variations in the store would just add to the burden.

But as to why it was a new version in the first place.. This is Apple's supported answer for paid upgrades. They did the same for Logic Pro X.

[100k]

I don't have a problem paying for an upgrade. There's features I am definitely excited about, like multiple Vaults which I mentioned above.

But as an end-user who only owns an iPhone, the only "feature" I notice in 1Password 4 for iOS is "Dropbox syncing still works". Not very compelling.

[astrism]

I think they do want the paid upgrade however I've gotten free updates to a great program since 2009. I have to agree that they have built an awesome tool that is incredibly easy to use.

[AGKyle]

AgileBits Support here.

Yes, this is basically it.

It was hard to pull our good friend 1Password 3 from sale, it still exists in the App Store, just not for sale. This allows purchasers to still download it, but it isn't for sale for new users.

One app is much easier than several. We had previously:

* 1Password for iPhone

* 1Password for iPad

* 1Password Pro (the two above as a universal app)

We did this because we released the iPhone app when they provided an SDK, and then the iPad was released but some users just wanted to pay for the iPad version, not the iPhone app again. So, we made it so users could do that, trying to provide a better price point for those users. For new users we stressed Pro for it's universal nature.

But, this was all very confusing. I can't tell you how many emails I answered that were from confused customers asking which one they would buy.

Having three apps was very hard.

This probably isn't the best place for this due to comment threading, but updating 1Password 3 for the newer Dropbox API would've taken a LOT of developer time. We did not use the Dropbox SDK because when we wrote 1Password 3's original code base an SDK did not exist, or if it did come out shortly after it wasn't acceptable for use for a variety of reasons, usually performance related. If I recall our developers correctly via various chats.

And if we did update for the newer Dropbox API then we'd be supporting two platforms (3 and 4) and it's just hard to do. Plus, the much bigger issue was we wanted to move the features of 1Password forward, for example, custom fields and sections. To get this support in 1Password 3 we would've had to have basically rewritten the entire data model and at that point all that's the same from the old app is the interface :)

The even bigger issue for a new app is supporting older platforms. Some devices can't run iOS 6, which 1Password 4 requires. Such as the iPad 1, which many users continue to use and love. If we had updated the app inline, those users would've lost the ability to download a working version if they needed to. This seems to have changed recently, as you can now download the last version to work for a particular iOS release. But this didn't exist last December, or leading up to release for months prior.

Now, hindsight being 20/20, many developers are doing new apps with regard to iOS 7 because it's a cleaner "break" and requiring more significant rewrites and provides a natural point at which to make a new app and charge for it. So, many developers are going through the same thing we did with iOS 6, but they're doing it with iOS 7.

Hope that provides some level of insight.

Kyle

AgileBits Support