cogitator@luurankosoft:~$ ./portofolio --serve --tone=devout [ 026.05.M3 // UPTIME 412d 06h 14m ]
cat ./identity.txt

> Hail, crawler/user. You have reached the cogitator-serving sub-vault of Luurankosoft, a sole proprietor concern: one skeleton, several machine spirits, indefinite uptime.

> Below: ./works, ./log, and ./contact. Press any key — or do not — to continue.

      
                  * *    
              *    *  *
          *  *    *     *  *
        *     *    *  *    *
    * *   *    *    *    *   *
    *     *  *    * * .#  *   *
    *   *     * #.  .# *   *
      *     "#.  #: #" * *    *
    *   * * *  * * "#. ##"   *
      *     * "###
             "##
              ##.
              .##:
              :###
              ;###
            ,####.
        /\/\/\/\/\/.######.\/\/\/\/\
// arbor cogitatus

./works — shipped artefacts [ 03 entries ]

001 skele-anatomy.app Educational mobile application for skeletal anatomy studies. Development further described below. TBD,2026? · iOS/Android
002 Luuranko.net This, self hosted site. Machine spirits willing, the server will be stable and it's resource usage wise, noospheric data-links stable. 2026 · Web
003 Luuranko.net Wordpress site for anatomical studies, flashcards. 2023 · Web

./log — workbench notes [ tail -f ]

ENTRY · 25.05.2026 · 1731H · 5 min read

On skeleton anatomy app, or how I despised wasting time and thus ended up wasting time.

> A simple solution for a simple problem. How do I make it so that 25 people per classroom don't have to waste hours upon hours making flashcards, that are not convenient or always with you? A simple problem and simple solution. That's where the questions and the quest for knowledge began.

> Initially there was a simple solution. A simple WordPress site, with a reasonably simple plugin for shuffling flashcards.

continue reading ▸ collapse ▴

> There's good enough and there's good enough. Ultimately, I was not satisfied with the wordpress site. The user-experience was lacking and in my hybris I was sure I could do better.

> A search for divided compromises. It was evident that a mobile application was warranted. That was the entire point of the project. To have your flashcards with you whenever you have time to study or unexpected downtime. Problem was that iOS and Android had different requirements, yet it would have been quite horrible waste to develop the same program twice.

> Flutter et .net MAUI Initially I had thought to write the application in C# utilizing .net MAUI. I settled on dart/Flutter though, after noting that Flutter was slightly more suitable for this use case, considering my own limited experience and better community support. Mature platform, no new surprises halfway through development, and somewhat maintained by Google, so android compatability hypothetically should be good.

> Doubts and unresolved questions: Unfortunately I have had not the time to release the software yet, and the project remains in development. The main questions I have are related to the somewhat unsavory aspects of monetization. I don't like the idea of despoiling the application with adds. Yet no-one will buy the app without the free version. And the student loan will need to be paid. So I suppose the rational thing to do is to release two versions. Free with adds and paid ad-free.

./contact — establish vox [ response < 3 rotations ]

EMAIL ········
INOP
TELEGRAM ·····
@luurankosoft
PGP ··········
INOP

Vox responses are dispatched as the machine spirit permits — usually within three rotations of the planet.