Page 1 of 1
new sagani interface
Posted: 22 April 2024, 19:01
by Phung7
that new sagani interface sucks bigtime. i wish developers/desigenrs would play a few games befroe adding brilliant innovations. last interface was not very good either, but at least it was palyable. now all good features are 'improved' while the really bad features are kept. why?
Re: new sagani interface
Posted: 24 May 2024, 17:41
by nogcrash
Agree! The tiles keep moving All The time, wich is so annoying, Every turn i have to re-center my tiles... pretty bad experience...
Re: new sagani interface
Posted: 25 May 2024, 02:06
by robinzig
Disagree - the latest change is a wonderful improvement. Previously, whenever I tried to scroll the page down - most annoyingly, on mobile - it would merely scroll my individual play area instead, when I really wanted to see other play areas, or the back of the tile on top of the stack. You had to find really tiny areas to use for scrolling to do this - it was just about doable, but not really friendly at all.
The new version eliminates that problem by having scrolling work completely normally as it does on any other game and webpage. I never actually raised this as a bug, and don't know if anyone else did, but I thank he developer for fixing i.
Re: new sagani interface
Posted: 21 June 2024, 14:37
by rroundabout
Definitely agree with @robinzig. I love the new update—MUCH more friendly for mobile users. Great job and thank you.
robinzig wrote: ↑25 May 2024, 02:06
Disagree - the latest change is a wonderful improvement. Previously, whenever I tried to scroll the page down - most annoyingly, on mobile - it would merely scroll my individual play area instead, when I really wanted to see other play areas, or the back of the tile on top of the stack. You had to find really tiny areas to use for scrolling to do this - it was just about doable, but not really friendly at all.
The new version eliminates that problem by having scrolling work completely normally as it does on any other game and webpage. I never actually raised this as a bug, and don't know if anyone else did, but I thank he developer for fixing i.