As developers building localized applications (like marketplace apps for regional users), managing multiple languages manually in OutSystems can be time-consuming. Currently, we need to export, translate, and re-import resources or manually edit translations. The Proposal: I suggest introducing an Enhanced Localization Tool within Service Studio that leverages AI and modern automation to streamline this process. Key Features: AI Auto-Translate: An option to automatically translate text strings into regional languages (like Malayalam, Hindi, Tamil, etc.) using integrated AI services during development. Context-Aware Translation: The tool should understand the context of a UI label or message to provide more accurate translations rather than literal word-to-word conversions. Visual Translation Preview: A feature to preview how different languages affect the UI layout directly in Service Studio, helping to manage "text swelling" (where some languages take up more space). Centralized Translation Dashboard: A dedicated dashboard within Service Center to manage and update translations for published apps without needing a full redeployment. Why it matters: This will significantly reduce development time for global and regional apps, improve the quality of localized user experiences, and make OutSystems a more powerful choice for building diverse, community-centric applications.

In modern mobile applications, notifications are key to user engagement. The Proposal: I suggest introducing a comprehensive Advanced Notification Management system directly within the Low-Code environment of OutSystems. Key Features: Rich Media Support: Ability to easily include images, videos, and icons within push notifications directly from the Service Studio. Interactive Action Buttons: Adding custom buttons within the notification itself to allow users to take actions without opening the app. Advanced Scheduling & Throttling: Built-in tools to schedule notifications based on user time zones and to limit frequency (throttling) to prevent spamming. In-App Notification Center: A ready-to-use, customizable UI widget that acts as an "Inbox" within the app to store and manage past notifications. Why it matters: This feature will empower developers to create more engaging and interactive user experiences. It will be especially beneficial for apps where real-time updates and quick actions are critical for success.

Implement an active Artificial Intelligence prompt directly integrated into Service Studio / ODC Studio, capable of analyzing OML files to detect issues, suggest improvements, and propose corrections , both automatically and through clear, detailed explanations of the proposed solutions . The idea is to allow developers to select a module or a set of elements (Actions, Aggregates, Entities, UI, integrations, etc.) and request an intelligent analysis that can: Identify logic, performance, security, and best-practice issues Suggest architectural and code readability improvements Clearly explain the root cause of each issue and the recommended solution Optionally apply automatic fixes or generate assisted refactoring suggestions An initial approach could involve exporting the OML for analysis by an external AI model (such as ChatGPT or Claude). However, the key differentiator would be having this capability natively embedded within the Studio , removing friction from the development workflow and improving application quality directly during development. Modern development tools already leverage AI for code review, refactoring, and optimization , delivering measurable gains in productivity and code quality. Bringing this capability deeply into the OutSystems platform would deliver significant value to developers , reinforcing OutSystems’ position as a leader in intelligent, AI-assisted low-code development.

The current Community platform suffers from performance limitations and provides a restricted level of user interactivity. To improve the overall user experience, I propose migrating the Community to a Reactive Web architecture within OutSystems. The growth and increased user engagement in the OutSystems Community can be attributed to a more intuitive, faster, and interactive experience that encourages users to actively participate, share knowledge, and return to the platform more frequently. Let’s move forward with this improvement to unlock a faster, more engaging, and truly collaborative community experience for all users. This is a developer’s observation based on system usage and user experience.

Enable to Test an Action giving new input parameters.

As AI and Large Language Model (LLM) integrations become more common in OutSystems applications, developers need better ways to monitor and manage how these services are used. Currently, when calling APIs like OpenAI or Azure OpenAI, developers must manually track important metrics such as token usage, latency, errors, and estimated costs. This is repetitive and usually implemented differently in each project. This idea proposes a Forge component called AI Observability Toolkit for OutSystems that provides a standardized way to execute LLM calls while automatically capturing key metrics such as: Prompt and completion tokens Total token usage Response latency Model and provider used Estimated request cost Execution status and errors The component could optionally store this information for monitoring purposes and include a ready-to-use Screen Template (AI Observability Dashboard) that developers can select when creating a new screen. This dashboard would display metrics like AI request volume, token usage, latency trends, and estimated costs. This would allow developers to quickly add AI monitoring and observability to any OutSystems application, helping teams better control costs, troubleshoot issues, and manage AI-powered features.

Would be a (minor) quality of life feature if you could bind a label to an input if you simply drag and drop it from the tool box on the left straight on the Input widget. For example here, this widget is bound to a "Max records" local variable, to control how many records an aggregate returns. If I drag the label on to it, it could do several things: Add the label on top of the Input Set the Input Widget automatically on the Label properties, and give it a name like "InputName_Label" Set the text for the label on a 'best guess' case, depending on what the input is bound to (for example here, Max records) This could work for all other input type widgets: text area, switches, checkboxes, dropdowns, etc.

Add an option in the Service Studio settings to disable automatic joins when adding new entities to aggregates. This is useful when there are multiple possible automatic joins. In many cases, fixing an incorrect join requires more effort than benefiting from the automatic behavior. Additionally, in more complex aggregates with many joins, it becomes harder to manage and verify which joins were automatically added and whether other entities were also included automatically.

Full widespread support for null values, in all layers: database, actions, ...Not fake zeros disguised as nulls, but real thing, the ones that we can compare to is null. The ones that mean "I don't know the value for this... I don't even know if its zero"

Add a way to filter the logs by excluding keywords. Use case : one of our process calls an external API using ArdoHTTP and every call results in a SLOWEXTENSION log, thus flooding the general log with pages of useless logs. This makes trying to find significant logs very difficult and time consuming. Being able to filter out by keywords, ie SLOWEXTENSION, would solve this issue.