Classic game for your wrist.</p><p></p><p>Merge numbers by tapping up, down, left or right until you get 2048 and win a game.</p><p></p><p>If you are developer or want to make feature/bug-fix request you may want to look at game source code (https://github.com/Tkadla-GSG/garmin/tree/master/2048-ish).</p><p></p><p>Software development is entirally coffein based. You can buy me a coffee (using https://ko-fi.com/tkadla) if you enjoy this game.
- connect iq updated</p><p>- support for additional devices from Approach and Edge families</p><p>- there is now 20% chance of spawning 4 instead of 2 as specified in game rules
Carter Bernard
September 8, 2021 |
Version 1.3.0
It hard works if I were you don’t buy this and buy it where it is where your the run and bike are
Ellie Barker
May 21, 2021 |
Version 1.3.0
Love this widget it’s so easy to use! And the game is so match fun!
Guillaume
August 10, 2020 |
Version 1.2.0
Très bien adapté à l’écran tactile rectangle de la Vivoactive HR
J_j
March 18, 2020 |
Version 1.2.0
The game wont pop up on my watch or the Garmin watch app thing. The problem is that the app that you are reading this on says that it is installed. What in the world do I do??
Simon Schaal
February 7, 2020 |
Version 1.2.0
Great game to begin with, and made perfectly for a smart watch! Thanks a ton!
Nicole89
November 19, 2019 |
Version 1.1.2
Hey, why is it not clearly visible which button you have selected?
August The Pilot
October 21, 2019 |
Version 1.1.2
On vivoactive keeps going to another widget. Also no score. Would also really like to see a high score
Quinn
January 4, 2019 |
Version 1.1.2
Fun, but after I lose a game, I have to uninstall and re download from the store. Am I doing something wrong?
Unkn0wnname1992
February 2, 2018 |
Version 1.1.0
Hi. Nice game but after losing the game my vivoactiv hr make reboot. Is it ok?
Developer Reply
February 11, 2018,
Tkadla
Hey, it is for shure not OK :). That being said, I do not see how can widget cause device reboot... at worst case, app should fail with IQ error, but device should be able to continue working. I did improve some parts of code 1.1.1, that could theoretically cause such strange behavior. Please let me know if if does not help with issue.