karnagebitcoin
commented
1 year ago @Egge7 just following up to see if you saw this.
Open karnagebitcoin opened 1 year ago
karnagebitcoin
commented
1 year ago @Egge7 just following up to see if you saw this.
Hey folks! @Egge7 asked me to take a look at current again so I did.
Please check this video: https://www.dropbox.com/scl/fi/u10ecf844jzlkqlyhcdtd/current.MP4?rlkey=o1ljnkkerv0ft66yuzdtfdzk3&dl=0
Here is a summary of some of the findings / opinions / recommendations (check video for full comments):
The welcome screen introduces keys right away. This may be confusing to people who are not familiar with what keys are. Recommendation: Consider a more traditional approach with login / sign up terminology and UX.
Some of the UI elements felt small / not taking advantage of full mobile width. Recommendation: Consider exploring other app UIs to see how they handle inputs to see if you can maximize the space in Current.
The NIP5 / lightning address selection might be confusing as people may not know what they are selecting. Recommendation: Consider adding explainers or eliminating that step entirely and defaulting them to one option or none at all (let them explore it in options).
Premium upsell is a bit confusing in language where it says zaps are paid, yet you advertise the tipping address. Recommendation: Consider making zaps a part of the free experience and clear up the copy to make it obvious people don't need to pay to use those features. IF you do plan on keeping as is, consider clarifying what those things mean and how the paid tier differs from free in terms of zaps.
I had a difficult time finding filtering in search. Recommendation: Consider moving filtered feeds / filters into the main feed area.
At some point I was unable to click on notes to see comments or reactions. Recommendation: Look into this issue to see if there is some technical issue for new users. Consider testing your onboarding periodically with non-tech-savvy users.
The app felt married at the hip with Bitcoin. This is cool if you are intending it to be for Bitcoiners. However, the general audience might think that this is some sort of a social network for "crypto" people. Of course this is just my opinion - I would test this theory further with real users. Recommendation: Consider testing your onboarding periodically with people of different backgrounds to see what goes through their minds when they see all of the copy associated with Bitcoin. You can draw your own conclusions whether it's fine as it is, or if the concept of bitcoin should be de-coupled from the concept of nostr.
The "Find people you know" screen did not seem to work for me and returned some other people who I know for a fact I don't follow on Twitter (X). Recommendation: Check to see if this step works, if not consider removing or fixing.
Recommended users seem to be randomly picked and mostly bitcoiners. If the audience is bitcoiners this is probably ok. But if you are trying to appeal to a broader group of people, this may harm the first impression of the app. Recommendation: Consider offering a step before the recommended users that allows people to pick some topics / hashtags to follow. If technically possible, consider surfacing users who post under those topics / hashtags and recommending them instead. At the very least, you can also consider showing trending users via nostr.band.
Toggling people to follow / unfollow all at once would have been a nice convenience.
Many / most of the posts seemed to have a lot of empty space. I eventually guessed that perhaps there is a minimum height set on them so that you can show the images you have set as background (I am assuming this). This felt like a broken UI and I was expecting images to load but nothing loaded. Recommendation: Consider this entire element layout and whether it makes sense to set images full width as a background. I personally think it does not, unless you are going for a TikTok full width scrolling (which again to me feels incompatible with notes).
The note comments view seemed to put too much emphasis on reactions, make it feel as though they were images or causing the UI look blended in without clear delineation of where notes start and end. Visually it's just a lot to process. Recommendation: Consider removing the backgrounds from reactions and spacing elements together within a note, to clearly separate from other notes. Right now you have a border and I think that works well as long as the elements are grouped in such a way that it's clear where one note ends and another starts.
The DVM looks awesome! But, my first remix did not work. Not the ideal first try UX. The follow-up attempt did create an image but it was not clear whether something was happening in the backend or not. Recommendation: Consider adding a loading state of some sort to indicate that the job is being processed. This will help ease uncertainty by letting people know it's just working and takes a bit of time. You can also estimate how long an average job takes and add that in the loading state copy "May take up to 30 seconds" for example.
The status button felt out of place under the main create button. Most clients handle status under profile, and although that's an extra tap / click to access, it feels a bit more intuitive than when creating a note. This is not a major issue I think, but something to think about. Recommendation: Consider testing with existing users or by asking for feedback from the general nostr community if having status in "compose" view makes sense or not.
In direct message tab, it was not clear what I'm supposed to do right away. Recommendation: Consider adding a default empty DMs placeholder or image that makes it clear I have no messages. Then, consider adding a compose button to start a search and or additional copy to explain that users should search for users to start a conversation. You do have an input placeholder that does this but it's difficult to notice and a bit vague.
I recommend checking out https://nostrdesign.org/docs/intro/ and corresponding "Reference Designs" figma file for ideas. I'll be updating this resource often.
My overall impression is that with some UI, typography fine-tunning and the tweaks outlined above, Current will be in a good place!
Please let me know if you have any follow-up questions, I am happy to look into anything else for you. 🙌