This is part of a response from mSecure in a different post - I thought it would be useful to see the current development priorities under Feature requests:
Thanks for creating this post. You aren't even interested in bug fixes though? :-P
Yes - bug fixes I guess get highest priority - especially if they have even the slightest impact on security - although to be honest I haven't come across anything on Windows or iOS that I would regard as a bug
I agree with Andy. Browser plugin/extension...this will just drain resources away from getting mSecure 5.x back to the functionality and speed of mSecure 3/4. Restore *all* of the previous versions features then add stuff like "Team/group options" whatever that means. This is a software for the person (hint: person) to store their passwords. How on earth would a group/team use this software?? Anyway, tackle bugs and security always first.
Beyond the ability to remove custom icons on iOS/Mac, what features is mSecure 5 missing? Please note that there are features that will likely simply not be carrying over, ever, such as the ability to change the record type of a record and(or) Airdrop support.
I'd like to make a case for moving #8 - Team/group options to your dev backlog for 2 reasons.
Andy is just an mSecure user (a great one) and does not work here at mSeven Software. With that said, we are currently working primarily on implementing a browser extension/plugin and a robust sharing feature. Our sharing feature will allow you to both provide a subset of records to family and coworkers (Dev teams).
Here's a preview of how our Sharing options work. Please note that this is an early example. We will be working on refining the look and feel of this as we continue to polish the feature:
You will be able to invite users to share "Collections" of records and provide the user with either a read, write, or admin privilege . Read privilege will make it so that a user can only view the record. Read privileges will not allow a user to edit or remove a record. A write privilege has the read privileges in addition to being able to edit and remove the record. A Write privileged user cannot change a record's Collection and has no ability to make changes to the "Collections" sharing properties. Lastly, the Admin privilege has all the read and write privileges and can also change the "Collections" properties by changing the name of the collection, deleting the collection, and adding and removing users from the collection sharing. Admin user can also change a record's collection as well.
This sharing feature will help immensely - thanks for the update!
So each record can be assigned to zero, one or many collections?
Does this work only when using the mSecure cloud - presumably these secondary users do not need mSecure installed or a copy of the database? Would this work with a WiFi master database?
Does the master user retain complete admin authority for all collections (or do you have to create another user who has to be assigned a role and access when using the plug-in)?
Great questions here.
Please let me know if you have any other questions about either feature here.
Thanks - not something I would use as I'm reluctant to rely on the mSecure cloud but I can see why you would do it that way.
My bet is that you will end up with irritated users if you don't allow a many-to-many relationship between records and collections - but hopefully others who would actually use the function will join in and give their opinion.
Our syncing methods all share the same methods and levels of encryption and security. Whether you use our syncing method or WiFi syncing, no one is going to be able to get your 45 character account key or be able to unencrypt it in order to access your information either locally on your device or in any system online. I'm happy to go over our security here if needed. All that said, we are not requiring users to use our sharing features nor switch to using mSecure Cloud syncing now nor in the future. mSecure Cloud syncing simply provides a perfectly centralized system to set up the roles, acls, and security needed for the sharing features to work.
We did make a mistake in the past not listening to the WiFi (smallest but most vocal) and iCloud/Dropbox crowd. That was a mistake and we are still sorry about initially releasing mSecure 5 without those additional sync options. We've apologized about that in the past and I'm happy to do that here again. However, this is not the same. If you could let me know how we are currently not listening to you, our customer, I'd be happy to take that feedback to others in her the company to improve our product and our roadmap as well.
To recap what we are working on currently:
Beyond the initial features mentioned on this topic, we are also currently working on (all currently in development):
And these are features we are looking into for the future as well:
All these features are based on user feedback mostly through our email support system and the the Feature Request section here on this forum. Please let me know if you disagree, hate, or dislike any of these upcoming feature or planned features. We would also be happy to hear from you exactly what features you'd like us to work on, fix, or upgrade in our app as well.
Not sure if you were looking for feedback on the plans but here goes:
Here are my top three requests-
"Improved Groups ability and(or) tagging system - Down the road" I'm disappointed this is not a higher priority as its the number one feature that would make mSecue even more useful for me.
Its useable today but once your passwords get into the hundreds in would make everything faster if there was a way to have multiple, dynamic groups of easily accessible "favourites".
"PDF attachments on all platforms (Ideally, I'd like to have all file attachment possible with a size limit)". I'm sure many people use mSecure as more than a simple password manager and this would go a long way to make this possible (storing ID cards, insurance documents, passport, rsa key files etc etc).
I don't see any features that would make mSecure more suitable for those geos where financial organizations require entry of selected characters from a password (for example if your password is "MYPASSWORD123" they might want characters 2,4 and 6 so you enter "Y","A" and "S"). Currently this can only be done by counting characters - or maybe splitting the password into groups of characters - but a simple format change in the app would simplify things.
I don't care about anything else on the list.
Hopefully the "smallest but most vocal" group of users can continue to impact your development priority.
And as Matt said 11 months ago "Browser plugin/extension...this will just drain resources"