Roadmap
Changelog
new
Environment Variables support has come to Uiflow! Create environment variables and assign values that correspond to our three environment contexts. You can find the new feature by clicking on the
cog
icon in the header of studio:
CleanShot 2023-05-25 at 15
CleanShot 2023-05-25 at 15
Use these variables in component
state
and
actions
with the following notation
{{env.keyName}}
and values will be pulled based on the environment.
CleanShot 2023-05-25 at 15
improved
All Project Types
Quick update on some tweaks to feature navigation in studio. In order to make room for some exciting features we have coming this year we've released a couple of tweaks to where you find some of the features in studio.
image
New
Pages
Tab
We have a new top level
Pages
tab. In this tab you will be greeted with a sub header that includes the familiar
Design
and
Logic
tabs. Whenever you want to edit the pages of your application you will find those tools here.
Auth
Tab
Authentication has been moved out of
Connect
and into the header as its own space for easier discovery and access.
Connect
Tab Publish Button
We've moved the
publish to logic
button into the
Connect
tab subheader. We've also updated the language around pushing your app from
Publish
to
Deploy
in order to disambiguate it from publishing other assets and better reflect what is happening behind the scenes.
image
fixed
improved
Feature
Web Project Types
Your authentication provider will now be used for authentication in live preview! This means you won't have to deploy your application anymore just to test login, logout, and authenticated flows against your provider configurations.
Just click on the
play
button at the top right of studio to launch the live preview experience. Note: authentication will still be mocked in the embedded preview experience within Logic.
CleanShot 2023-05-17 at 08
Alongside this update we squashed tons of bugs throughout the authentication experience within Uiflow so if you haven't given it a shot yet there's never been a better time!
new
Feature
Hey everyone, we are excited to announce the launch of our teams features alongside a migration to workspaces and a revamped dashboard to wrap everything together.
Workspaces
This change is mostly under the hood but everyone has been migrated to workspaces. When you create an application it will belong to one of your workspaces. You can swap workspaces via the switcher found at the top of the sidebar in the Uiflow dashboard.
image
Teams
You can now invite team members to your workspace. All team members will have access to any application inside the workspace and you will be able to collaborate together in real time. This is a very exciting launch for us and we can't wait to see what everyone creates together.
To invite a team member, click on the sprocket icon next to the workspace switcher and click on the
Invite Team Member
button of the
Team
tab. Note: You must be an Admin or Owner of the given workspace.
image
You can find more information about teams and workspaces in our docs: https://uiflow.gitbook.io/uiflow/studio-overview/workspace-management
Dashboard
As you explore these features you will notice we've given the dashboard a fresh coat of paint. We are continually working to improve the dashboard experience so let us know any feedback or questions you might have about the new design.
improved
Feature
Web Project Types
Uiflow has released highly requested updates to the
Connect
tab to make building your connection components even easier!
Table View for Objects
You can now construct objects in the
Connect
Tab using a key/value table and expose specific keys in your connection components to simplify usage. This works for any object type value across all connections.
CleanShot 2023-04-19 at 08
CleanShot 2023-04-19 at 08
Path Parameters
For REST API connections, you can add path parameters using the
:variable
notation, which automatically creates a node for the variable on your connection component.
CleanShot 2023-04-19 at 08
CleanShot 2023-04-19 at 08
new
Feature
All Project Types
For those of you that keep up to date with our change log we have a treat! We've released a secret alpha of Figma import! You can open up the new feature via
cmd + shift + f
. All you need to do is make sure your file is set to public. Again, this is currently in alpha so not everything is implemented at the moment but please send feedback to us via email or discord.
2023-03-22 09
new
Components
All Project Types
Take actions using our new Uiflow slack bot integration straight from Studio.
2023-03-22 09
improved
Feature
All Project Types
Quickly select multiple components in Layer and Tree panels via
Shift + Click
2023-03-21 16
new
Feature
All Project Types
2023-03-07 14
For when you need to select many components at once, now you can use
Shift
+
Left Click
to lasso select any number of components in your flow!
new
Feature
All Project Types
Hey everyone! The team has been hard at work on something very special over the past few months and we are excited to finally share it with you all!
2023-03-02 16
Today, we release a new version of Logic in Uiflow. Before we get into the specific changes and how they work, we want to share a bit about why this re-architecture was necessary and how it sets us up for future releases.
Anyone who has built apps in Uiflow knows that Logic is displayed and embedded within your app’s tree. Design and Logic used to exist together since they relied on each other’s positions to function. This worked well for simpler apps since you could always find the logic for a given piece of UI.
However, as users built more complex apps and collaboration became more common, the existing Logic framework became fragile and unsustainable. Some of the biggest problems we wanted to tackle with our redesign are:
  • Designers editing an app’s UI and breaking the logic.
  • Excessive numbers of interface node connections between components.
  • Difficulty troubleshooting logic.
We've been using our updated Logic for a while now and love it, we can't wait to hear what you think!
Logic Flows
CleanShot 2023-03-02 at 16
  • Separation of Logic and Design
    :
    Logic Flows
    no longer include
    Design Components
    . This means you no longer risk breaking your logic when you make changes to your design.
CleanShot 2023-03-02 at 16
  • Multiple Flows per Page
    : You can now create multiple flows per page, rather than a single flow for all your logic. This is perfect for separating logic concerns such as
    Get Data
    ,
    Authenticate User
    ,
    Send Data
    , etc.
Design References
2023-03-02 16
With the addition of
Logic Flows
, we added a new concept to help build logic for your designs.
Design References
are scripts associated with each
Design Component
for your app’s UI. These
Design References
appear in the
Logic
view and enable you to add interactivity to your application without limitations from your design structure. You can even include multiple
Design References
to the same component, to organize complex interactions. To add a
Design Reference
to your flow, simply drag a
Design Layer
into your
Logic Flow
.
Collections + Constructors
CleanShot 2023-03-02 at 16
Collections
and
Constructors
are inherently related to each other and their children. When you place design components inside a
Collection
or
Constructor
, each instance is expected to include all internal logic and designs. To ensure this integrity in
Logic
, child components of
Collections
and
Constructors
are disabled in the
Design References
section until you enter the parent component. In short,
Collection
and
Constructor
children can only be added to
Logic Flows
inside of their respective parent.
Migration of Existing Apps
CleanShot 2023-03-02 at 16
All existing apps have been automatically migrated to our updated
Logic
framework. To ensure each application works exactly as it did before, we:
  • Migrated existing logic on each page to a new single logic flow, which contains all your pre-existing logic.
  • Preserved all existing connections and hierarchy.
  • Added a new logic component type called
    Group
    (represented in orange) to maintain any nesting components that existed prior to the migration.
Load More