It’s Great

Hi,

Thanks for the review, and for trying Keyy!

The plugin does not support login through mobile devices via the mobile app (but Clef did)

Keyy does support that…. which OS are you on? On Android, it’s the “Browser login” link. On iOS, it’s the link “Login on this device’s browser”.

There’s no override URL, in the case of emergency.

Interesting idea! I’ve added it to the list. Can you describe more how you’d like to see it work? (N.B. I have never used Clef).

Note: This review stands true until the next update.

Please do come back and review when it’s out! (Or even now, if you spot the browser login link).

Best wishes,
David

My two-penneth worth…

Overall so far so good with Keyy – a little dismayed by the pricing given Clef was totally free – however, if it’s lack of funding which is why they Clef is going then maybe fair enough. Was gutted when I heard, but then was pleased to hear you guys were doing it. You will have a ready market, but people will be sensitive to the price. I was using UNLOQ.io since Clef’s announcement. Not quite Clef, but close, but it is entirely free too. So just making that observation.

Re Point 1 – I know the “wave” is coming soon – to me that’s really just cosmetic – definitely looks cooler, but the functionality is the same. So no biggie for me

Point 2 – Agreed – the functionality to login via a mobile app on the mobile device’s browser is there and works fine.

Point 3 – the override URL was the only thing I too wanted to ask about too. Keyy “locks” out the registered user (whether you want that or not) so that they can ONLY login via Keyy once reg’d. Now, Clef had a few check box options around that on the settings page on the dashboard – here’s a couple of them…

– Show ONLY “wave” so all users must be reg’d with clef (and use it) to login. I.E. It was optional. Yes, I would usually have it enabled, but you could flip-flop if needed. I tended to disable all these option elements before creating a staging copy of the site – otherwise I was always locked out on that site due URL differences etc.

– You could chose to show both login options (trad. login and clef), but you could still in this case choose OPTIONALLY to force clef users to only be able to login via clef or not.

So if you had the first one set (disallowing any traditional login), or you allowed both types of login, but disabled traditional login for a clef user – and you messed up clef somehow and were locked out, that’s where the override URL came in. The generated URL took you to a login page on the site (with a “key” in the URL) that would allow anyone with that URL to login traditionally – whether a clef user or not (so you needed to keep the URL safe).

It was a nice saftey net.

Hope that helps clarify.

@ankushdas @adz1111 – the override URL is in the release version now (end of last week, IIRC).