Githawk: TestFlight beta feedback for GitHawk for GitHub

[Maryom]

Hi,

Thanks for sending me the TestFlight.

So far it’s good. I didn’t find any bug. I just have some suggestions:

1. In the settings view I think there is no need for app ID near the version number.

2. Kindly check the attached image. Why there is an UIActionController with one option?! It will be better if the action triggers when the user click on GitHawk.

Best regards,
Mariam AlJamea.

[Maryom]

Hello again,

One more suggestion if you don't mind: I really like how GitBucket implements the time line. I would like to see it on GitHawkApp :)

[Maryom]

Hello again,

Today I found an issue. My inbox was one, I used GitHawkApp to reply to the message. It replied successfully but it should remove one from the inbox and display Inbox zero with the awesome animation 🎉 Kindly check the attached image.

Thanks.

Best regards,
Mariam.

[BasThomas]

Hey @Maryom, you can turn on “read on open” in the settings. That will mark an issue as read once opened. Is that the behavior you’re expecting?

_{Sent with GitHawk}

[Maryom]

Hey @BasThomas,

Thanks for this awesome repo. Yes, you are right. I should turn it on. Well I think it’s better to make on as the default value. What do you think?

Best regards,
Mariam.

_{Sent with GitHawk}

[BasThomas]

@rnystrom re the alertcontroller actionsheet in the original post: how do we want to handle this? Just opening it directly also feels weird having the chevron. What do you think?

[Maryom]

@rnystrom re the alertcontroller actionsheet in the original post: how do we want to handle this? Just opening it directly also feels weird having the chevron. What do you think?

@BasThomas what about adding it to this alertcontroller 👇🏼 ?

_{Sent with GitHawk}

[BasThomas]

The tricky thing is that we already use the navigation bar for the exact functionality (opening either the org/user and repo), but from a repo overview itself that only leaves the org/user. Putting that in the ... is also confusing.

[rnystrom]

Ya I'm not terribly concerned w/ the single-action alert. It's nice that it's consistent w/ the rest of the app, so you expect it.

[Maryom]

As you like

_{Sent with GitHawk}

[SD10]

Well I think it’s better to make on as the default value. What do you think?

I think making "Read On Open" the default value doesn't demonstrate this feature very well. And this behavior is one of the main reasons I use GitHawk. I often check an issue on GitHub, intend to reply later, and 💨 it's gone forever

[Maryom]

Hello,

I noticed that number of messages in the below view 👇🏼is less than the real number of messages

_{Sent with GitHawk}

[BasThomas]

What about after a refresh?

_{Sent with GitHawk}

[Maryom]

What about after a refresh? ...

@BasThomas same issue

_{Sent with GitHawk}

[rnystrom]

Do you have a screenshot of your actual notifications? I feel like there was an issue where the API doesn’t return historical notifications (stuff prior to using GitHawk).

_{Sent with GitHawk}

[SD10]

It probably wouldn't hurt to start opening separate issues for different pieces of feedback/potential bugs. I'm pretty out of date with GitHawk at the moment but I'm having trouble following this thread 😅

[Maryom]

@rnystrom No I don’t have

_{Sent with GitHawk}

[rnystrom]

+1 @SD10 that’ll help us keep hinges tracked and organized

_{Sent with GitHawk}

[Maryom]

Ok I will open new issues if I find new ones 😅 sorry I thought I have to write all my feedback in one issue.

_{Sent with GitHawk}

[BasThomas]

Closing this as I don't see any clear action points in this issue anymore. :)