Big News! Split to be acquired by Harness. Read More
Users can now categorize their organization’s most important metrics as “guardrails”. Guardrail metrics are those your organization wants to protect during a feature release or experiment. Metrics are set as guardrail metrics for your workspace on the Metric definition page.
Using the latest Split SDKs, users can more easily define targeting rules for new features based on app, OS, and other versions using attribute-based targeting. The SDK then automatically serves the appropriate treatment to users without needing additional code configurations. Split’s native Semantic Versioning Targeting removes the additional complexities and manual work that comes with targeting different application versions, allowing users to seamlessly deliver different experiences.
Left-hand navigation within the application has been optimized. With this change, we’ve narrowed the navigation bar, migrated the search function to a modal dialog, and moved account settings to the bottom of the page. This makes frequently used actions (e.g. workspace switching) more readily accessible within the UI.
Users can automatically capture event data in Split using their iOS SDK without needing additional agents, integrations, or track calls. This eliminates the manual process of sending events to Split, allowing users to quickly set up metrics and alert policies.
Split automatically creates metrics for any events being auto-captured by the Split Suite and RUM Agents (Web, Android, iOS). This reduces the manual effort of creating metrics and allows users to easily calculate their engineering and performance metrics.
Users can now use Switch, Split’s in-app AI assistant, to easily summarize their experimentation results. Simply click on any metric card and hit the summarize button for a full analysis of your data. Please note, that this is a Generative AI feature that leverages end-user/customer data and will only be available to users who have specifically requested it to be enabled via Split’s Support team.
To help teams easily coordinate and collaborate on flag updates, we added shareable direct links to change requests. This allows teams to quickly share feature flag updates with key stakeholders and get faster approvals when needed.
Users can cancel a response from Switch mid-flight. This allows users to move forward quickly in cases where they asked the wrong question or if the response they needed was already on the screen.
Users can now also copy code snippets directly from Switch, enabling faster time to value.
To help teams quickly find the information they are looking for, Split has improved the filtering experience in these lists: feature flags, segments, and metrics. Users’ most recent search filters will be preserved as users continue to navigate the product.
Users can now reduce the minimum sample size to 100 at the organizational level via the admin setting. This allows users to get statistically significant results, faster.
Toast notifications will now appear in the lower right corner of Split’s UI. This increases the visibility of the notification and enables users to easily take additional action within Split.
Users can now automatically capture event data in Split for their Android SDK without needing additional agents, integrations, or track calls. This eliminates the manual process of sending events to Split, allowing users to quickly set up metrics and alert policies.
Users can now automatically capture event data in Split for their Browser SDK without needing additional agents, integrations, or track calls. This eliminates the manual process of sending events to Split, allowing users to quickly set up metrics and alert policies.
With RUM Agent iOS, the iOS SDK will automatically capture event data and send it back to the Split Cloud. Event data will then populate in Split’s Data Hub, similar to impression data. This eliminates the manual process of sending events to Split and enables a quicker setup of metrics and alert policies.
Split’s React SDK hooks can now return the SDK’s readiness status and support update parameters to control when an application will render. These properties now allow users to easily refresh application components with just a few lines of code.
The useSplitTreatments hook has been optimized to detect duplicate getTreatment calls, improving the performance and UX of the application.
Dynamic Configuration’s JSON input field now supports text wraps. This allows users to easily view and edit content that contains very long strings like prompts for Large Language Models without needing to scroll horizontally across the screen.
With Flag Sets, users can group flags that logically belong together, so that the SDK only retrieves relevant flag definitions when initialized. This reduces SDK latency, memory consumption, and CPU utilization.
We’re excited to accompany you on your journey as you build faster, release safer, and launch impactful products.
