Logging in to apps
I'm a new user. I bought the app after hearing almost universal praise for it. Seems like it might be really useful on my Mac, but it's borderline useless on iOS for me. I use iOS for 90% of my computing, and I would estimate 70% of the time I need a password it is to log into an app. The percentage of apps on my devices that are on your list is in the single digits. I have a couple of comments, questions, observations or complaints (depending on how you want to look at them).
I don't care about the money, not much anyway, but I have invested so much time just trying to figure out how to use the software. The 2 times I tried to use it on a webpage, it didn't work, and as established above, it doesn't work for any significant portion of my apps. The documentation seems written in such a way that I had to search the forums after giving up and piece together a vague understanding of how to use the software from several sources. There aren't any simple, clear step-by-step or walk-through YouTube videos. I'm just trying to make the point that it's somewhat unintuitive and complex, thus better guides or learning aids seem warranted. This seems to marketed as a mainstream solution, not a niche app - but the documentation and support are at odds with that. The nomenclature is unclear, not even sure which category to choose for a given type of data/password.
I assume that it's a restriction of iOS that prevents 1Password from working with any app - is that right? If so, why aren't more developers on board with the premier security software? They are constantly updating, and 1Password has been available for months. What is the roadblock or downside for them? Is it possible that it won't be necessary for them to alter their apps in the future, or is this dependent on developers participating?
I'm just frustrated, perplexed and disappointed that despite the cost and effort, I just have keep logging into apps just like I did before. The entire concept of 1 Password is defeated by this shortcoming. I would have just sent this in an email to support, but when I click the "contact" tab on your site, the only email options are for a lost license or to subscribe to the newsletter.
What are the workarounds for getting password (and possibly username, etc.) info into apps?
I'm hoping to get some answers and maybe have a little confidence restored. Maybe even encourage agilebits to invest in some easy to follow training videos.
Comments
-
I have the same issues when trying to use 1Password IOS and the many apps on myiPhone and iPad. At one time 1P was able to insert/interact with Apps but according to AgileBits Apple's changes to the OS forbids this interaction. AgileBits response to me over a year ago was to use 1P and get to the site you want via the browser. This isn't a very good solution because often Mobile Apps have features that don't exist on the browser's site. Like you I find this to be a pain, accessing my apps is slow and very cumbersome, needing t o cut paste user names and passwords. Using the 1P solution makes having apps on you IOS device a waste of time. I sure wish they would design a work around or persuade apple to allow their integration to be tighter.
0 -
I have same thoughts as second thoughts. I purchased this few days ago also after reading all praise thinking that is i now have more complicated PW they would autofill especially my banking mobile apps sites. No way just copy and paste. I thought i missed something with instructions etc not thinking it is not integrated in the software. I also have macbook air and will admit PW5 works as advertised but i prefer to use my mobile device. For me bottom line this product is not air time ready for mobile users. I use TDBank, vanguard( that was fun trying to get this used//pw to autofill, not), USBank and Chase mostly, so any help for iPhone 6 IO8 would be appreciated.
0 -
I believe I am correct in saying that until iOS 8, apps could not interact with each other, so cut and paste was the only way to get passwords from 1PW into an app. The introduction of iOS 8 allows an interaction, but it is new enough that most apps have not yet been updated to hook into 1PW.
0 -
Actually I used to be able to use Apps and 1PW to autofill my user name and PW but i believe it was around the time OS7 was introduced that the wall was set between apps and 1PW's ability to autofill. In any case, cutting and pasting makes the 1PW user experience very painful. I also use banking apps and many other apps on my iOS devices and in most cases the app has mobile device friendly features that I want to use, that are not available on a web browser. i.e.: deposit check. This makes me fight through the pain each and every time I need to insert a username and password in the mobile app, which is always. For this reason I've greatly reduced my use of 1PW and limit it to on my PC and MAC, until they figure out how to get this to work and improve user experience. By the way!, the other things that bugs me (I'll post elsewhere as well) but I don't like the idea that my PC version of 1PW is different than my MAC; like having a wallet on my PC version that went away on my MAC.
0 -
The thing is that the mobile apps need to hook into 1PW to accept passwords without copy and paste. And this is an issue on their side, not on 1PW's. 1PW provides an extension that apps can use to hook in to it. But this concept of extensions is very new, and most apps have not yet been adjusted to accept it.
You would be doing yourself and others a favour if you asked your naps, and similar organisations, to update their app to use the extension.
0 -
Thanks for all the responses. You may be right Danco. One of my questions was what the impediment was for app developers - whether it's a particularly onerous or difficult task to implement, whether they aren't getting adequate support from agile bits, whether they don't want to bet on one solution over another, or whether they haven't gotten around to it?
As I indicated, I've already found it a lot of work already to use the app, on top of the expense. I have over a hundred apps - I'm not particularly inclined to try to reach out to them and be an evangelist for 1Password, when I haven't gotten a response from agilebits yet. For all I know they are on the fence about continuing to develop or support iOS, or are getting a lot of pushback from developers.
If I didn't have an iPad, I'd probably be pretty stoked about the app. As it is, I'm often stuck with nothing but an iPad, and I have to write down about 56 passwords, and reference/
use them fairly often. Which means I'm nowhere close to one password. I have yet to hear a clear explanation of the workaround (or if there is more than one, or an endorsed one).I haven't given up, but I've stopped putting effort into it. I've had to enter 3 passwords today. Really shouldn't be up to me to figure out the workarounds, or to ascertain the status or level, of interest from what number of developers. I'll either regain some interest in putting effort into it, or it will fade and I'll use keychain. As I said initially, I was hoping for some information and encouragement from Agile bits. Meanwhile, I'm going to sleep on it.
0 -
Hi folks,
@danco hit the nail on the head in this post: https://discussions.agilebits.com/discussion/comment/160504/#Comment_160504
Developers need to add 1Password support, we can't force them to do so. As to why more apps aren't doing it, yet, anything I could say would be purely speculation. I can say though that more and more developers are working on it, and we've recently been added by some pretty big names such as WalMart. :)
The best we can do is suggest that you, as a customer, contact the apps you use that do not have 1Password integrated and request they do so.
Thanks.
Ben
0 -
I'm not exceptionally technical and I already have a full time job but the responses I hear from Danco & Ben make me pretty sure I need to stop using 1password. I think their suggestion is a huge ask. I remember when 1password used to work with my mobile apps without the need for me to tell the developer they need to make a change that allows their app to work with 1pw. Is there a list of app developers who have taken this type of direction? Chase Bank, Wells Fargo, Bank of America don't care a flip about me requesting they alter their apps to work with 1pw. Not sure if I'm in the minority but I'm not convinced 1Password's a household name yet. And I'm certain app developers are more likely to take this type of direction from a company like Apple, where companies want to align with their strategy. I think I now need to find an alternative to 1pw that works with iOS.
0 -
Hi @Bill Sanders
I'm a bit curious as to how 1Password used to work with your mobile apps. As has been mentioned above, prior to iOS 8 there was no way for 1Password to fill in another app. Apple had some pretty strict regulations in place governing how apps could interact with each other. In short, unless the app included support for 1Password explicitly, 1Password could not do anything (like filling) in another app. These sandboxing restrictions also prohibited 1Password from providing browser extensions for mobile browsers. Usernames and passwords had to be copied from 1Password and pasted into the log in pane of the app.
The announcement of the app extension in iOS 8 made our developers literally dance in their seats at the Apple event, because it opened a whole world of potential for 1Password.
Of course, we're not simply relying on users to spread the word about our app extension. We've been reaching out to developers everywhere to encourage them to implement the extension, and we think we've had some pretty great responses so far. You can check out Apps that Love 1Password to see all of the apps who are already 1Password-compatible. Although we are doing our best to get the word out there about 1Password, it can only help if users such as yourselves reach out to developers and let them know that you would be interested in seeing 1Password support.
I hope this helps explain the situation just a bit better. :)
0 -
I too share some of Secondthoughts frustration. Guess there is a fine line between security and convenience when it comes to running apps. Would like to see in future updates where we can select what we want to insert from 1P (user id or pw) if auto-fill does not work. I'm sure other developers would not like to open their apps for security reasons also.
0 -
Just to reiterate: The only way, currently, for iOS apps to interact the way folks want them to (e.x. 1Password being able to fill credentials into another app) is for those two app developers to work together to make that happen. That is the only way that Apple currently allows such integration. We've published a guide to help other developers add 1Password to their apps:
It is up to those developers if they wish to do so, and to actually implement it. The suggestion to do so coming from us doesn't mean much, but if their customers contact them indicating this is something that they want, they are more apt to listen.
We have a large list of apps that have already added 1Password:
I doubt you'll find another password manager for iOS that can make that sort of claim.
Thanks.
0
