How are all the SaaS builders creating consistent UIs?

Tips & Tricks
, ,
1

Hi all,

I’m building a SaaS app (like an industry-specific CRM) and I keep running into challenges keeping UI consistent using Agent - specifically when I have options to Create new records, View the record, and Update the record. Agent tends to produce a different visual experience, introduce or change fields, make changes to schemas, APIs, and the list goes on, needless to say though it’ll only match from front end, middleware, and backend for one of those forms.

Does anyone have best practices on how they ensure consistency in their apps to support CRUD functionalities in their app when they have separate pages for Add/Update/View?

2

For the front end, you can use something like bootstrap or tailwind as a starting point to then modify/override. I don’t use the agent but use the assistant and when something like bootstrap is my baseline, things generally come out looking very consistent. For a new app I might start something like “We going to build X that does Y. Let’s start using bootstrap, create a base template and separate styles file, and we’ll be using dynamo for DB and S3 for object storage…”

1 Like
3

This right here :backhand_index_pointing_up:

4

At this stage, I’m not confident I could migrate over to Dynamo and S3. I’m using Tailwind, Postgres, and Drizzle :frowning: .

5

I am using the same as you. I was referring to the process night runner was describing.

6

Agreed I wouldn’t touch any db or storage but maybe switching to specific asks of the assistant or agent to leverage tailwind buttons and interactions could help the UX consistency.

7

Got it, just need to read up on Tailwind I think to understand the functionality better. Appreciate the feedback!