-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profile screen in SwiftUI #963
Conversation
Going to post some issues I have seen in TestFlight here. Will put them in separate comments as maybe that will help track which ones have been fixed. I'll put checkboxes on them too in case that is helpful? I don't think we get the "Resolve conversation" button unless I comment on a specific line of code. |
|
Just verifies that I am still seeing it. Here's a video of my exact steps. If you still can't reproduce then I can check out the branch and do some debugging. RPReplay_Final1668703525.MP4 |
Sorry @mplorentz but that's not the build I sent today. Its still processing I think. |
@martindsq For the pressed state we can invert the colors of the button in both light and dark mode. Here's a preview: |
This is a very good suggestion, @mplorentz . Here's a smaller collapsed version of the profile card: |
@martindsq Here's an animated prorotype for the collapsing of the profile card: Screen.Recording.2022-11-17.at.18.34.37.mov |
I think we should probably limit the user's name to one line? Although it would feel bad to truncate people who just have long names. Maybe we need some guidance on how to make long names look good @Chardot? |
@Chardot I think we could use some kind of placeholder for when a user isn't following/followed by/ignoring anyone? |
…tary-social/planetary-ios into feature/about_view_swiftui
I went ahead and made it a two line limit label (because we can), and instead of using the full identity when the name is not available, it now uses the short identifier
Fixed this
When implementing the profile screen I asked this same question and he preferred to show it as it is. |
That's a very good suggestion. What about something like this? |
Closes #681, #976, #977 and #961