The Game of Fifteen written with Flutter
Clone or download
Latest commit 5986300 Jan 22, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
android Fix Google Play Games integration Jan 6, 2019
artwork Move to an immutable state architecture (part 3) Dec 30, 2018
ios Initial commit Dec 21, 2018
lib Make the complexity of 5x5 puzzle more consistent Jan 22, 2019
screenshots Add README.md Dec 30, 2018
test Initial commit Dec 21, 2018
.gitignore Initial commit Dec 21, 2018
.metadata Initial commit Dec 21, 2018
LICENSE Initial commit Dec 21, 2018
README.md Add link to Play Store Dec 31, 2018
pubspec.yaml Bump version to 1.1.4+10 Jan 22, 2019

README.md

Game of Fifteen

Main screen: Light

Main screen: Dark

Puzzle game with Flutter?

The Game of Fifteen (also called 15-puzzle, Gem Puzzle, Boss Puzzle, Mystic Square and many others) is a sliding puzzle that consists of a frame of numbered square tiles in random order with one tile missing.

Get Game of Fifteen on Google Play

Report a bug or request a feature

Before creating a new issue please make sure that same or similar issue is not already created by checking open issues and closed issues (please note that there might be multiple pages). If your issue is already there, don't create a new one, but leave a comment under already existing one.

Checklist for creating issues:

  • Keep titles short but descriptive.
  • For feature requests leave a clear description about the feature with examples where appropriate.
  • For bug reports leave as much information as possible about your device, android version, etc.
  • For bug reports also write steps to reproduce the issue.

Create new issue

Creating your Game of Fifteen

We welcome all developers to use our source code to create applications on our platform. There are several things we require from all developers for the moment:

  1. Kindly do not use our standard logo as your app's logo.
  2. Please remember to read and follow the license.

Versioning

For transparency in a release cycle and in striving to maintain backward compatibility, a project should be maintained under the Semantic Versioning guidelines. Sometimes we screw up, but we should adhere to these rules whenever possible.

Releases will be numbered with the following format: <major>.<minor>.<patch> and constructed with the following guidelines:

  • Breaking backward compatibility bumps the major while resetting minor and patch
  • New additions without breaking backward compatibility bumps the minor while resetting the patch
  • Bug fixes and misc changes bumps only the patch

For more information on SemVer, please visit http://semver.org/.