Hi, I don't want to create a general "What is the future of Buzztouch" discussion (although it may be interesting). My current situation is that I used Flutter for different apps (iOS & Android, Web Apps) in the last years. In such apps there is always a question of what to use as a backend for the app. Last week, I repeated my search for Flutter backends, and upon reviewing the options, I realized that I have access to a fairly flexible app backend on my self-hosted BT server. The flexibility was very important for letting my clients edit the features in the app that I created for them (adding items to lists, or even creating new screens of a specific list design). When I think about the other backend options (Firebase, Backendless, Appwrite,...), such flexibility and comfort would require an additional frontend to talk to the app backend in a user-friendly way. To be honest, I have not succeeded in updating the Android version of my Buzztouch apps in the last months. And that is the reason why I do not dare to use Buzztouch for future apps. So my idea and/or question is to evaluate the following workflow: - Keep my BT server just for acting as an app backend, where I can add additional functionality ("screens"), and where my clients can update the content of their (Flutter) app easily - Use the great backend features of BT to create JSON data when the Flutter app asks for updates - Dissect the JSON data in my Flutter app and create a similar app flow (clicking a list item brings the app to the screen associated with that item...) I guess that it would not be a simple job to do, but similarly to the "screen/plugin" structure of the BT apps that could provide a general Flutter app structure that might be used in different apps. My question: Would that be a good idea? I ask that question to you BT members... but I was curious and asked ChatGPT as well. Here is the response: I evaluate Buzztouch from two perspectives: technical and strategic. Technical Pro: Very flexible, server-side control, individual customization possible. Cons: - community practically no longer active. - Android builds increasingly difficult due to SDK changes, Google Play requirements, lack of maintenance. - Security patches and API adaptations are up to you. - Framework is no longer optimized for today's mobile standards. Strategic If you primarily use Flutter now, you already have the advantage of a cross-platform code base. So all you need is a stable backend that: - is API-capable (REST/GraphQL) - database, user management, push, possibly media management - is maintained in the long term ... so here it is back again... the question "What is the future of Buzztouch?" in the form of "is maintained in the long term". ;-) As I do not want to rely solely on ChatGPT, I am interested to see your comments! Best wishes Thomas