Testflight version 1.5.1

[hape42]

I have rebuilt a lot in the code. All the pages that can appear during a game, such as messages, invites, scores and much more I have outsourced in the code. On the website, this was always displayed on an extra page. I made my life harder than I had to by trying to display this so that you could still see the board.
When you describe problems, the device and the IOS version should always be mentioned.

minimum feedback for all should be something like: "tested on iPhone XR IOS 16.1 no problems found so far".

thank you and happy testing

[kagsteiner]

Thanks, looking forward to testing it. Great reconstruction work it seems. So far only few open matches so I can't test much.

[kagsteiner]

Played a number of games on

• iPhone 12 Pro Max
• iPad pro 12.9 inch
  both with latest iOS / iPadOS
  All went well, no crashes, no issues. New screeen seen that tells me current standing incl. (predicted result). Nice :-)

[Smiles2go]

Apologies if I misunderstood. Still, it feels like something has changed regarding end-match messages on iPhone -- seems like I get fewer offers to send messages or replies than I used to.

No, please don't invent new send-message prompts that don't come from the html.

Possibly consider adding a send-message button at end-match if it is easy to tell who message should go to.

[Smiles2go]

Is Gitlab working? Guess so. Couldn't save a message or upload picture yesterday.

There are confirmed strange things with the new messaging full-screen format on iPhone. They are not severe problems, but more symptoms of DG's difficulties having no coherent and consistent approach to in-app messaging.

It is hard to test because the new screens don't come up often, and there's no way to tell if a composed message was sent or not, received or not.

And with iOS Display Zoom is enabled, compose box falls off bottom of screen, possibly sometimes along with buttons.

Here's screenshot of message on iPad followed by same message on iPhone 14:

I didn't realize the black box was for message composition.

Turning off Display Zoom works better, though when composing a message, there is no button for Send or anything else visible. Fortunately tapping outside message box caused keyboard to close and presents buttons.

Similar issues with some messages sent by other players. I couldn't get this on two different devices or with/without Display Zoom maybe because it isn't tied to current match. So messaging was working but wasn't obvious big box within big box was for composition. No prompts or option to quote previous text as before.

So the full-screen messaging and compose works on iPhone, even in Display Zoom mode. Some prompts (that don't become part of the message) would help "Enter message here..." or "Enter reply here..." depending on situation. For replies, re-add "Quote received text" button. Add a "Done Editing" button when keyboard is up.

If text has been composed, maybe change button names to "Send then Next Game" and "Send then To Top". Is usually some way to elect to not send a composed note, so maybe add explicit "Send" and "Don't Send" buttons is better.

(What happens if outbound message was composed and user hits hamburger button in top-right instead of a button at bottom?)

[hape42]

sorry to see that.

I understand your problem with the iPhone, large font, keyboard, text box, etc.

It is on the iPhone in landscape mode now just very little space. I have also just looked at WhatsApp. They also have a similar problem as me. When the keyboard is displayed, there is very little space left for a text field in landscape mode.

Unfortunately, I must admit that I can not solve this satisfactorily.

I still program mostly alone. My capacities are not sufficient to dedicate myself to this topic adequately.

Of course I don't want to disadvantage anyone with a visual impairment.

But the topic is so big for me, I will not be able to solve it satisfactorily.

The app was originally programmed by me for the ipad. Adapting it to the iPhone causes me more problems than I ever thought.

Maybe it's better to take the iPhone variant out again altogether?

[Smiles2go]

No... please don't kill iPhone support. It is still way better than the naked web browser.

Thanks for what you've done. I'm sorry if I seemed too critical.

[kagsteiner]

Totally agree with @Smiles2go - I'm playing most of my matches on the iPad, but it is totally great to be somewhere else where you only have your phone (doctor's waiting room, for example) and have a nice UI to play DG on.

[kagsteiner]

Found a bug :-)
If you do the following:

1. Ensure that the connection to the server is not blindingly fast :-)
2. Click “lists”
3. Click “active matches” and “active tournaments” repeatedly really fast, back and forth, faster than the app can update
4. App crashes (you should have received a crash report)

Tested on iPad Pro 12.9, iPadOS 16.4.1

[kagsteiner]

Another very minor thing that is strange is: If the server is slow or I have a very long list of matches, top page acts like this:

1. show empty list
2. Show pop up „getting topPage Data“
3. List is populated and active and usable
4. pop up still stays there for seconds

In this situation I can click on a match and play, but I‘m still wondering what the app is still retrieving from the server and why the pop-up doesn‘t go away.

[kagsteiner]

Playing in that tournament that feullesmortes is organizing. Many many parallel games. App behaves perfectly well. :-)

[J1Moyer]

I want to help testing, this is my email address: [email protected]

[kagsteiner]

A friend mentioned that he would like to have a more thoughtful button placement. In some situations some buttons should have the same location on the screen, so that you can just keep clicking for default actions.

Example:

• Roll Dice -> submit greedy bearoff" - would be good if the buttons would have the same location.
• Submit -> Next (ie you submit a move and then see the opponents' move) should be at the same location.
• Roll Dice -> submit force move -> same

Counter-example:

• Next (you see opponent move as first thing in next match) -> roll dice/double : the two buttons should be on different location than "next" on purpose, because there is no clear next default button and it's bad if the app would guide me into not considering doubling.

Tricky because there are so many different situations...

[hape42]

To avoid misunderstandings, we should always try to support such topics with screenshots and possibly sketches in the screenshots. A good way is also to show how it is presented on the website and what is missing in the app to make it at least as usable as on the website.

You can open an issue on this topic to show what needs to be done in one place.

[hape42]

done