This is more a question but I guess it also may be a re-wording request.
Once inside an issue you have click the titlebar to get an action sheet that says @GitHawkApp and then GitHawk. @GitHawkApp will take me to the GitHawkApp homescreen in webview. If this is just a link to the Organizations page maybe a rewording is in order. @Organization doesn't make me think I'm going to be redirected (Could be just me, I associate it with a message or something). The GitHawk option / Repo option opens the repo in app, this one makes a bit more sense but some clearer wording could still be added I feel. Even if it was. View Organization, View Repo or something like that.
The @ is supposed to denote a user/org. The thing I like is that the words are connected to the button you just tapped.
Adding “View” before each word wouldn’t hurt tho!
Sent with GitHawk
Ya view @GitHawkApp could clear it up a bit
Sent with GitHawk
I feel like the @ and no @ are already tricky sometimes, especially with repositories like Moya/Moya. Anything that can make it more clear is 👍
Maybe an icon that represents an organization and one that rep. A repo?
Along with the view @. And view
Sent with GitHawk
Wait yeah we could add images with https://github.com/BasThomas/ImageAlertAction :)
Boo ya!
Sent with GitHawk
Organization Icon: https://octicons.github.com/icon/organization/
Repo Icon: https://octicons.github.com/icon/repo/
@BasThomas That was easy. Great pod!
So thoughts?
Sent with GitHawk
Ehhhj it’s overkill IMO. Adding “View” makes it pretty clear.
I’d actually rather use ContextMenu for everything.
Sent with GitHawk
I think the view @GitHawkApp is a bit cluttered but otherwise I felt it was clear. You could probably go with either icons and not “view” or just view.
Sent with GitHawk
I think it might also be the outlined image (for repo) vs the filled image for organization.
I agree with Ryan that consistency with ContextMenu would be really nice though :)
Ya I think I rather both by outlined. Context menu would probably look nice as well. The feeling I get with context menu is that it's been used to "act" in the app. Assign labels, milestones..etc. Hopefully change the current branch (#1582). I guess since all it's doing is redirecting, context menu may be unnecessary.
Hm, good point. I feel like it could indeed be a bit too big of a context switch (ugh, no pun intended). I guess we can play with it and revert to what we have / this if the context menu doesn't work out.
In general I think both are a step in the right direction — I still get confused between @ and non-@, and any help disambiguating the two is greatly appreciated.
Something else we should keep in mind are the icons. A repo can also have an owner instead of an organization, and it would be nice to be able to have separate icons to indicate that.
Agree
Sent with GitHawk
@rnystrom @BasThomas So whats the conclusion on this one? Context menu or UIAlertController? Icons/No Icons (If yes, outlined/filled) ? View/No View?
Aside: If we could add grey description text underneath the text we could get rid of the word view and clear things up a bit in the process.
After some more thought I'm leaning towards the UIAlertController with icons. If Ryan still prefers the ContextMenu, it would be nice to compare them!
@rnystrom Context menu or UIAlertController
Closing as #2135 was merged
Sent with GitHawk
Most helpful comment
Wait yeah we could add images with https://github.com/BasThomas/ImageAlertAction :)