UX Help welcome

THIS IS A READ-ONLY ARCHIVE OF THE SQRL PROJECT FORUM

Hi @Mark_roudebush

I'll try to answer your questions and I will take the liberty to rephrase some just to clarify how I've understood them.

The timeline is sadly a little vague to me and I've not created any milestones at the moment. I had small milestones during the development process so I could separate out the development of key features and have a bit of a timeline until feature completeness.

I think the application is feature complete except for functions that I put into the "like to have" features. Two I can think of is Biometric keys instead of password and share files with the application for import. Not crucial for the release of the final application.

My intention has always been to release version 1.0.0 of the application when Steve decides to go public with the application so could we hit that mark that would be wonderful but I have so far work incrementally with the project as I have limited time. Now we are a few developers so we have a bit more time but I still want to keep ownership of the releases and merge process of the changes which can be a bottleneck.

When it comes to the iOS the developer is @Jeffa.

I'm not sure if there is anyone responsible for the Web experience. There is an extension implemented for web browsers but each site owner will be responsible for their site. So in the case of the forum, I look to @Steve but if there is a WordPress plugin in the future for instance then the owner of the WordPress block will be responsible for that experience.

Open source projects seldom have teams but more contributes. By that I mean that people contribute their time, you can't assign time they need to work on the project. But so far I've seen contributions from @sengsational, @sesam and @Janne Oksanen. I'm truly sorry if I'm forgetting someone.

But this is a community effort so anyone may contribute and the important part is to create clearly defined issues to solve on Github so contributors may put in the time and solve these. Then I will look at these contributions and decide if they should be merged into the project or not.

I will release when something is ready for release.

When it comes to stakeholders I'm not sure. @Steve is responsible for the project as a whole, he is the inventor and the community have together created this solution, it has iterated a lot of the last 5 years. A year ago I looked at the project again after a long hiatus and realized that the current implementation of Android applications was stale.

I decided that this project needs an Android app and I've built a few in my life so I thought it would not be that hard to create one. I think the first implementation was done quite quickly. Then I've iterated slowly. Done some bug fixes and solved some UX problems but as my expertize in UX is limited this process is slow and tedious so that's why I reached out for help.

Best regards
Daniel
 
  • Like
Reactions: Mark_roudebush
Hi @Mark_roudebush

I'll try to answer your questions and I will take the liberty to rephrase some just to clarify how I've understood them.

The timeline is sadly a little vague to me and I've not created any milestones at the moment. I had small milestones during the development process so I could separate out the development of key features and have a bit of a timeline until feature completeness.

I think the application is feature complete except for functions that I put into the "like to have" features. Two I can think of is Biometric keys instead of password and share files with the application for import. Not crucial for the release of the final application.

My intention has always been to release version 1.0.0 of the application when Steve decides to go public with the application so could we hit that mark that would be wonderful but I have so far work incrementally with the project as I have limited time. Now we are a few developers so we have a bit more time but I still want to keep ownership of the releases and merge process of the changes which can be a bottleneck.

When it comes to the iOS the developer is @Jeffa.

I'm not sure if there is anyone responsible for the Web experience. There is an extension implemented for web browsers but each site owner will be responsible for their site. So in the case of the forum, I look to @Steve but if there is a WordPress plugin in the future for instance then the owner of the WordPress block will be responsible for that experience.

Open source projects seldom have teams but more contributes. By that I mean that people contribute their time, you can't assign time they need to work on the project. But so far I've seen contributions from @sengsational, @sesam and @Janne Oksanen. I'm truly sorry if I'm forgetting someone.

But this is a community effort so anyone may contribute and the important part is to create clearly defined issues to solve on Github so contributors may put in the time and solve these. Then I will look at these contributions and decide if they should be merged into the project or not.

I will release when something is ready for release.

When it comes to stakeholders I'm not sure. @Steve is responsible for the project as a whole, he is the inventor and the community have together created this solution, it has iterated a lot of the last 5 years. A year ago I looked at the project again after a long hiatus and realized that the current implementation of Android applications was stale.

I decided that this project needs an Android app and I've built a few in my life so I thought it would not be that hard to create one. I think the first implementation was done quite quickly. Then I've iterated slowly. Done some bug fixes and solved some UX problems but as my expertize in UX is limited this process is slow and tedious so that's why I reached out for help.

Best regards
Daniel

Thanks, very helpful.
I really appreciate your perspective of releasing when it’s ready.
 
@kalaspuffar @Mark_roudebush happy to help out with UX if needed. I am a UX Architect working for a health and wellness education company operating on the US healthcare and employer markets. Former life experience in ad agencies, strategic marketing, product dev, and research, before moving to UX a few years ago. I am currently involved in various new product development and also dealing with enhancements of current platforms and apps. Profile here FYI https://www.linkedin.com/in/florina-visinescu-9118324/
Pls give a shout if anything.
 
I'm here for assistance as well. 25+ years of IT experience.
Efficiency expert, and am good at QA testing as "grandma" :)

To be the kind of successful we all hope for the app is going to have to be built for her/him.
 
Hi @FlorinaV

Thanks, I want everyone to be able to come with suggestion and feedback. And I will probably be the judge if the things suggested will be implemented/included. Then again I'm not a UX designer so I can see if something is working and I can create good UI but handling differing requirements, finding a common path for UI and expressing a good UX design in a way that we can reason about to find any major flaws is very time consuming for me as I've not had much experience with it.

I want someone to take the lead and work to resolve this lack of clarity.

So, for now, I asked @Mark_roudebush to take the lead and he has asked a couple of questions. But at the moment I don't know how the work progresses.

But all help you or anyone can help is appreciated.

Best regards
Daniel
 
Hi @FlorinaV

Thanks, I want everyone to be able to come with suggestion and feedback. And I will probably be the judge if the things suggested will be implemented/included. Then again I'm not a UX designer so I can see if something is working and I can create good UI but handling differing requirements, finding a common path for UI and expressing a good UX design in a way that we can reason about to find any major flaws is very time consuming for me as I've not had much experience with it.

I want someone to take the lead and work to resolve this lack of clarity.

So, for now, I asked @Mark_roudebush to take the lead and he has asked a couple of questions. But at the moment I don't know how the work progresses.

But all help you or anyone can help is appreciated.

Best regards
Daniel
Sounds good @kalaspuffar. I will reach out to Mark about this.
 
What might be helpful is to use an existing app as a model. If there's an existing app that we think has a UI that we think would be good to emulate, we could look at that. Of course the purpose of the app could be anything, since we'd just be taking best of breed UI ideas. Best would be something from FDroid (open source), but even something off of Google Play that we could all look at might even be helpful.
 
Some additional thoughts on identities. The interface should consider several items for managing multiple identities:
  • Be able to handle at least 1000
  • Have a “favorite” tag that would sort favorites to the top
  • Have a search for quick finding of identities
 
Hi @silversword

Great ideas if the app would keep an identity per site. The SQRL protocol is built in a way that you have 1 identity to rule them all.

If you have more than one identity you are an edge case and if you have more than 10 identities you are either a developer of the Android application or using it wrong.

That is at least my humble opinion.

Best regards
Daniel
 
  • Like
Reactions: leilabd
If you have more than one identity you are an edge case and if you have more than 10 identities

Or you’re an IT Consultant that helps others with their digital life which includes logging into their accounts and online services to help them manage their digital life. I’m definitely edge case but I currently have 200+ client LastPass passwords because they need me to be their technical backup. They don’t manage passwords properly, they don’t and never will know how to configure the ever increasing complexities of internet life possibilities/accounts etc.

I bring this up because if you want to design an app you should think about and include in your design the flexibility to handle all scenarios. The simplicity of passwords is the reason they’re used everywhere. Write an app designed for 20 years of possible use-cases. It doesn’t take much on the developer side to foresee the eventualities, and design/plan a layout to handle all the cases passwords handle. How are you going to help a spouse/child/family members etc if the world eventually adopts sqrl. It won’t take that much work on your part to make a flexible framework for your sqrl client.

An individual can easily have 3 sqrl profiles: personal, work, anonymous profile.
 
logging into their accounts and online services to help them manage their digital life
SQRL has a feature for this, if sites enable it. (Managed Shared Access.) If it does not support that, then it's unlikely you will be able to have someone else's identity to use... at least if they actually understand that allowing you access would allow you access to EVERYTHING SQRL in their life... banks, email, whatever. There is no way to extract "part" of an identity, at least as SQRL is currently designed.

3 sqrl profiles: personal, work, anonymous profile
I have been arguing this myself, but I am getting a lot of resistance. Steve recommends using Alternate IDentities for this (if indeed you use anything.) I am not sold on this concept.
 
  • Like
Reactions: silversword
SQRL has a feature for this, if sites enable it. (Managed Shared Access.)

Had forgotten about that feature...I don't really WANT full SQRL identity, it'll definitely be better to see proper Managed Shared Access implemented with SQRL adoption.

I fear server-side implementation of the feature will not be as ubiquitous as single user access because of the extra work for implementation server-side.

Thx
 
Alternate IDentities

I looked up the details on that. Yeah, you have to manually type in/remember a specific ID that's hashed? That will never be a real world usable feature except in extreme cases, fraught with user frustration from the start.
Completely impractical except for the super-security conscious that is ALSO a documentation freak...requiring explicit documentation outside of the Sqrl client for when backup/restore/device moves occur IF the data is even properly backed up/cached.
 
I looked up the details on that. Yeah, you have to manually type in/remember a specific ID that's hashed? That will never be a real world usable feature except in extreme cases, fraught with user frustration from the start.
Completely impractical except for the super-security conscious that is ALSO a documentation freak...requiring explicit documentation outside of the Sqrl client for when backup/restore/device moves occur IF the data is even properly backed up/cached.
Others HAVE proposed an enhanced client that remembers those, along with what sites the user has visited. Although, the alternate ID could be "2" and could be the same for any time the user has an alter-ego on any site.
 
I’m definitely edge case but I currently have 200+ client LastPass passwords because they need me to be their technical backup.
I don't think any SQRL client should cater to your use case. Nothing stopping you from forking some code and making it really easy to do what you want, but to put this into a typical client seems less than practical. I personally think the best mobile client opens to a QR scanning screen and can scan a login or an identity. If the latter, it replaces the one and only identity the client supports. If a login, it logs in. Done. If widely adopted, this mobile client will work for 99% of the users, given they have a full client on their desktop.
 
I don't think any SQRL client should cater to your use case.

This is a UX discussion, nothing should hinder a simple clean interface for the apps primary purpose. I'm talking about 3 well designed dialogs/interface elements that can handle all use-cases, and the needed data structures in it's database to store the needed data. Envision in advance for needed elements, and add them as-needed. You won't even see multi-identity capabilities unless you need them.

A great app has a clean interface, but expandable power when needed for all use/cases.