Kiwitrees on Twitter

    relationships, colors, flags, GDBR, person, DIV, fatal error, living, pdf, googlemaps, index, REFN, wish, transifex, Php 7.1, mobile, children, date, contacts, login failure, MAC, new feature, abbreviate, clipboard, album, ckeditor, GEDCOM errors, session, nickname, special character, margin, survey, Require visitor authentication, set link, Batch Updates, colors theme, translation, marriage, Extra menus, block, kiwitrees 2.0.2, logs, tags, contact links, lists, clippings cart, 3.1.1, default individual, access roles, upgrade, access level, partner, cookie, ID notes, places, title, emmigration, Default record, latest version, zend


    110 posts


    The move to a more mobile friendly kiwitrees is probably necessary. I just hope all the hard work you have done does not get destroyed in the process. I have seen several commercial sites that have gone down this road with disastrous results.

    Many of the conversions that I have seen resulted in a big user mess. Simple navigation clicks turning into multiple clicks to accomplish the same thing. Content that should be entirely on a single screen requiring several screens. As often as not, even the intended results were not accomplished. In most cases two distinct sites driven by a single content database would have resulted in a better solution.

    While I use a tablet and a IPOD Touch, I cannot think of a single reason for my using them as my primary genealogy tool. I might use them to show a casual contact some genealogy data but the power of the current kiwitrees is not necessary for that.



    Apache 2.4.27  PHP 7.19 MariaDB 10.2.8