Jan 19
Multilingual Apps
GB allows you to create the backoffice in another language (even with potentially different contents) to have many different ones.
However, during the login phase or with a special section, a list could be created that allows the user to choose the language and simultaneously select the relative back office.
Ex: I download the app (in the default language) I sign up and choose the language (it connects to the relevant backoffice).
I then have the possibility in my profile to choose whether or not to change the language.
Thanks so much
Pending
It would be better if it is more specific, like this I have two feature requests that I believe would significantly improve the GoodBarber platform, especially for apps focused on international users, tourism, events, and multilingual content. I would also assume that these are requests other GoodBarber users have raised before, as they address fairly common limitations when building content-heavy applications. 1. Seamless Multilingual App Experience GoodBarber should offer a more flexible and lightweight multilingual option that allows app developers to provide their own translations and let users seamlessly switch between languages within the app. The current multilingual solution feels unnecessarily complex and can increase the overall weight of the application, while not fully solving the needs of developers who already have their content professionally translated. A better solution would be: Allow developers to manually provide translations for the app interface and content. Allow users to switch languages seamlessly from within the app. Keep the translated versions within the same application rather than requiring separate language configurations that increase app complexity and size. Allow developers to manage and update translations directly from the GoodBarber back office. Preserve the same content structure, URLs and navigation across languages whenever possible. Allow each language to have its own SEO metadata, including translated page titles, meta descriptions, headings and other relevant SEO fields. Support multilingual SEO so that each language can be properly understood and indexed by search engines and AI search systems. Ideally support language-specific metadata such as hreflang, allowing Google to understand that different language versions represent the same content. Allow developers to optimize translations independently instead of relying entirely on automatic machine translation. For example, if an app is available in English, Mongolian, Spanish, French and Japanese, the developer should be able to provide and manage each translation directly. The user could then simply select their preferred language and the entire app interface would change without requiring a separate application or unnecessarily increasing the app's size. This would be particularly valuable for tourism applications, international businesses and apps targeting users from multiple countries. 2. Recurring Events The Events feature should support recurring events natively. Currently, if an event takes place every Friday, every Tuesday and Thursday, or on another recurring schedule, there does not appear to be a proper option to define that recurrence. The current workaround requires creating the same event manually for every occurrence, which is inefficient, time-consuming and creates unnecessary duplicate content. For example: Latin Party Every Friday Jazz Performance Every Tuesday, Thursday and Saturday Live Band Every Wednesday Instead of creating hundreds of individual event entries, the developer should be able to create one event and define its recurrence: Every day Every weekday Every Monday Every Friday Multiple selected days Weekly Monthly Custom recurrence Start and end date Optional exceptions or cancelled dates The system should then automatically display the upcoming occurrences while keeping the event as one manageable content item in the back office. SEO Considerations for Recurring Events This feature could also be extremely valuable from an SEO perspective. Rather than generating hundreds of duplicate pages for the same recurring event, GoodBarber could maintain one authoritative event page containing structured information about the recurring schedule. This would make the content cleaner for: Google Search Google Events AI search engines Local search Event discovery platforms Users searching for events by day The system could potentially generate structured event data using the recurrence information while avoiding unnecessary duplicate URLs. These two improvements would make GoodBarber significantly more efficient for developers managing multilingual applications and large event databases, particularly in tourism, hospitality, entertainment and local discovery applications.