These brand new mobile apps deserve their own topic!
Demo mobile applications that showcase some of the initial key features of the Alpha 2 SAFE Network. For now, only Android is supported in devices. These apps can be used in conjunction with the Alpha 2 desktop apps; the SAFE Browser and the Email/Messaging App.
I needed to give Firefox permission to be a source for the so called .apk files (Android Package, the bundle of the App). Android normally blocks other app sources and wants you to download all from Google Play. But when you download a .apk file with Firefox you are directed to the setting to change this .
After downloading both the Authenticator and SAFE Messages you can install them both:
Just tested the new Apps and I got several messages from people from tablets and mobiles. Of course I replied to them all using my Android! Very cool! I like to point out 3 things that are confusing to people and hope others can help think of a solution. I understand these are Apps to help devs outside of MaidSafe with quick start, so consider these findings for anyone that can work on the Apps.
You need to use the Authenticator at first to log on.
I know, that’s how SAFE works but it might scare some people a bit if they’re new to SAFE. Not a real problem though, because it’s probably the only way to go. Would it be possible to combine both the Authenticator and the App? Or maybe future Apps as well? That way each App would start the Authenticator in the background as part of itself. The SAFE Messages App would go from 60mb to 120 mb. And each other App would become 60mb bigger as well. And you would also need to check if someone already logged on using any other SAFE Mobile App. It gets confusing quite fast.
You need to log on every single time you use the App
A way around this is to protect the App with a pincode or Face ID or Fingerprint. So people log in once a week (also to make sure they won’t forget their log in credentials) but can authenticate with the Authenticator using a fingerprint or something for the rest of the week.
The Login button is out of view
When you log on to the Authenticator you’ll see this screen with a Login button:
The Log in button is gone, and to go from “Secret” to “Password” you need to remove the keyboard manually. I’ve tested it on several different Apps and found that most of the time the “Log in fields” and even the Log in button bump up to be all visible when the keyboard comes up. The Netflix App didn’t allow me to make a screenshot but that one works the same way. When you type in your log in credentials both the “username_field” and “Password_Field” and the Keyboard and log in Button are all visible. That way you type in the credentials and directly hit the Log in button without removing the keyboard.
Hope my explanation makes a bit sense.
Anyway, I guess the next mobile App should be a browser isn’t it?? . Firefox Focus is a mobile privacy friendly browser. Have a look:
@dammeul You may wish to get more specific support getting started by asking this question on the developer forum, under the category “Support”.
This weeks developer update had information relating to mobile …
“We have started to work on developer’s guide for .Net developers which help them while developing desktop and mobile apps for SAFE Network using .NET Core, .Net Framework and Xamarin. These guides will be published soon on SAFE Network DevHub website.”