Since I gave up on Apple and decided I don't want to pay that company money for nothing, I was searching for somebody who would distribute my MineSweeper application on iOS. At the end, the ControlsJS guys agreed to do it, but only if the application starts using ControlsJS. As a result of this experiment we now have two completely different UIs for the same application code:
- http://controlsjs.com/demos/minesweeper/ - the new Controls for Java version
- http://xelfi.cz/minesweeper/bck2brwsr/ - the original MineSweeper as written by me
Under the hood both versions are almost the same. They only differ in the rendering technology. All the other features - for example high portability remain:
- the iOS application: https://itunes.apple.com/us/app/controls.js-fair-minesweeper/id1110702611
- the Android version: https://play.google.com/store/apps/details?id=com.controlsjs.demo.minesweeper
Write Business Logic, Choose UI later
The code for the Controls MineSweeper is available on github: https://github.com/controlsjs/minesweeper. I was curious to see what code changes were necessary to completely switch from one rendering technogy to another.
While inspecting the code I noticed that the core application logic in MinesModel.java hasn't changed at all! It doesn't make sense to count one additional property and removed goto links handling due to simplified UI. Wow!
As an implication you can focus on your code, provide draft version of UI, and later, completely throw the UI away and redesign it in a much better way. Chances are high you will not touch your application code at all!
Moreover you can completely change the UI technology. Start with classical DukeScript solution and later switch to ControlsJS - given the rich set of tools ControlsJS offer including WYSIWYG form editor, it may really make your UI design experience smooth and even boost your productivity.