So thanks to the new version, I've got the capability for logos on my
tokens now. Awesome.
A few thoughts:
1. I've got what seems to be a bug with the new version on my Nexus 7.
Adding a new token via scanning a QR code works, but there's no feedback
to let me know that it works. The scanner just keeps turning and trying
to focus etc until I hit back. Once I do, I can see that there's
actually a new token. Fully reproduceable with github, which used to
work fine (old version). Haven't tried any other sites yet.
2. What are recommended sizes for images? How are non-square images handled?
3. Where did the devs get the logos used in the new screenshots in the
google app store? I'm having a hard time finding square logo-only images
online to use for this purpose (without editing). Perhaps we could have
an online repository for user-contributed images (hmmm... copyright ...)
that FreeOTP could connect to.
4. The image stretches to the very edge of each token widget/card (for
lack of a better word). From a UX perspective, I think it would be
better to force a border around it (meaning: the image will be a little
> > You might try googling "square $COMPANY logo" or other similar things.
> > ...
> Yeah I had been having a rough time finding good ones with google, but I
> had much more luck once I started using google's advanced search
> settings to configure the type as "clip art", the aspect ratio as
> square, and the filetype as png.
I've had pretty good luck searching for company "icons" rather than
"logos". I think that pretty much implies square, but I guess the
resolution might not go up that high (I didn't really care that much
about the resolution though).
Hi folks! Nothing much more than the subject says here. Just a simple RFE.
(Warning: my comments reflect the Android version.)
For the sake of clarity, what I mean is that it would be awesome if the
context menu on each token widget had a 4th entry ("Color...") which
would let you customize the color of said widget. I have multiple tokens
and being able to set custom colors for the more important ones would
make it much easier to choose them quickly.
Thanks for reading!
The past few weeks have seen new releases of FreeOTP on both of our supported platforms.
On iOS, we released a small bug-fix release to the initial version we published several months ago. Aside from a crasher bug, the main theme of this release is UI refinement.
Editing and reordering is now modal. When in edit mode, a single press will bring up the edit menu and a long-press will activate reordering. We also now properly handle scrolling when there are too many tokens for the screen. Lastly, the token is automatically copied to the clipboard when activating a new token code.
All in all, this is a solid release.
On Android, we released a major release which brings many new features and UI refinements. The biggest of these is image support. Images can be selected for each token. Images can also be provisioned to the device via an undocumented OTP URI query parameter. Aside from image support, the UI has begun to shift towards the Material Design specifications (for the upcoming Android L release). This includes a change from the card UI to a grid UI. Additionally, like iOS, tokens are now automatically copied to the clipboard.
One note about permissions is necessary. In the new Android release, the INTERNET and READ_EXTERNAL_STORAGE permissions are now required. In the latter case, this enables us to read images stored on the external storage. In the former case, this permits OTP token provisioners (the people who give you the QR code) to bundle a link to a token image. We feel this features is worth the additional permission. In the case of iOS, FreeOTP already has these permissions and uses them responsibly. Android will be no different. If you don’t trust us, you can read the code.
If you are running CyanogenMod, or have installed an app which allows you to manage permissions on installed apps, you can feel free to turn off the internet permission. You will not lose any functionality except automatic provisioning of token images.
How can I backup existing tokens in order to later add them (e.g., on a different device)?
Is there a way to restore the tokens other than manually entering the info?
Sent from my mobile device.
CAUTION: FreeOTP has moved to a new token storage system internally.
This transition should be seamless. However, there is a risk this beta
application may eat your token data. Please back up your codes or have
another device handy before testing this application.
* Moving towards a Material Design UI, incl. image support
* Support for opening token URIs from the browser
* Support for provisioning a token image via QR code
* Updated QR scanning code
* Numerous bug fixes
We came across your mobile app and we wanted to get in touch with you. We are AppVJ, a video production company that produces animated explainer videos and marketing videos for mobile applications.
All our videos include HD Quality video, professional voice over and licensed background music. You can review our work samples at www.appvj.com. You can also find plans and pricing information on our website. Plans begin at $199 for a 1-minute long video.
Please reach out to us if you have any queries or need clarifications. We look forward to work with you!
PS: You can Unsubscribe by responding to this email with an empty message and you wont hear from us again.
I am using FreeOTP v.1.4(13). In what format should the QR Code be for
sending the base32 code to FreeOTP?
Simply sending the text for the code in base32 causes the app to crash.
I also found a reference to sending the code as follows:
What should the text in the QR Code contain so that the app doesn't
crash? And shouldn't it ideally give an error message instead of
crashing, if the code is incorrect?