Great news from GitHub - they started beta stage of Discussions feature and SQLiteStudio project has it enabled already. From now on instead of creating an issue to ask questions and discuss, you can use the Discussions exactly for that: https://github.com/pawelsalawa/sqlitestudio/discussions. All issues labeled with "discussion" or "question" were converted to the new Discussions items.

What's already done

• New home page. Obviously.
• CI/CD with GitHub actions. I've already set up pipeline for unit tests per commit + 3 pipelines for building Windows/Mac/Linux binaries with just one click. This removes impediment of building binaries for each release, which was a headache so far.
• Installer (Qt Installer Framework) is removed from the application. We're going back to portable packages only (i.e. download, uncompress and run). When I was introducing it in version 3.2.0, I wanted solution that is well tested and will make automatic updates for users easy. Instead it introduced more issues and bugs into the application, made binaries way bigger and complicated releasing process even further. I decided to remove automatic updates, but the application will still check if there is new version released (on GitHub) and notify user if there is (offering link to click). It's just that it won't install it - user will have to download and install it. Maybe in future I'll consider other installer framework(s).
• Windows 64-bit binaries. Yes. No longer 32-bit binaries for Windows (which was often a trouble when working with huge datasets).
• SQLite2 and Android plugins are removed. They were very rarely used and caused a lot of maintenance effort.
  • SQLite2 is old. If you need to open it, use older SQLiteStudio, migrate to SQLite3 and move on.
  • Android plugin was far from ideal. To make it usable at decent level, it would require lots and lots of work. Also, I'm convinced there are better, dedicated ways to deal with SQLite databases in Android applications. I'm not an expert, but I think even Android Studio does it well.
• SQLite3 version updated to 3.30/3.31 (depending on certain plugins, not all vendors are at 3.31 at the moment when I'm writing it). Currently this is just about having recent database engine & syntax assistance, that will understand window functions and other new features in pure SQL queries. It will require more work in future to provide UI clickable interface for these features.
• Facebook page has been decommissioned. I'm not active FB user and I was always late with answering questions there. It is also yet another place to put time & effort to, while it's not really beneficial to the project.

Of course there is many more bugfixes and minor enhancements coming in next release. You can track it on GitHub.

Plans

There is few things on my TODO list that I consider critical. They will not necessarily go into next release (which is mostly about bug fixing + few small enhancements), but are high on my priority list.

• Proper theming, with few pre-defined themes, including dark. Currently theming & color configuration is a nightmare.
• UI simplification. There is too much buttons at first glance. It should be more intuitive. Overall UX should be improved.
• High DPI support. Icons in the app are not scalable. SVG iconset should be used instead.

Soon after 3.2.0 few major problems appeared, which are addressed in 3.2.1.

One was inability to start application under Linux, second was missing Image previewer plugin in binary packages. Both problems were caused by incorrect packaging scripts. There was also one more smaller bug regarding data exporting (see ChangeLog for more details).

If you're upgrading automatically from 3.2.0, after you're done, you need to run the "UpdateSQLiteStudio" from application's folder, pick "Add or remove component" option, on next page expand the tree and mark "Image editor/viewer plugin" and proceed with installation. If you're installing/downloading 3.2.1 from homepage (and not through the auto-update), you will already have this plugin installed.