4 ms·

Cool stuff, I've considered building something similar for my own needs. For me, I would never invest the time to learn and integrate something like this into

Cool stuff, I've considered building something similar for my own needs. For me, I would never invest the time to learn and integrate something like this into my business processes if its not open source. But there is a large market of folks who don't care about that (obviously, as Salesforce isn't open source and does well enough), so you have a lot of potential. I played with the demo for a couple of minutes- one thing I noticed was that to add a field, you have to go up to the drop down menu in the top right and select add field- I would expect to see an "add field" button below the (initially empty) list of fields on an object. Hotkeys would also be really nice at some point as you develop the app. Probably just really early in your development to refine these things. You mention your path to success being a "modern UX" and I think that is great, if by "modern UX" you mean (at least in part- a major part) "much faster and more responsive than Salesforce". Maintaining the flexibility while also keeping it easy to use and fast is a triple combination of power.

noleary 3y ago
Awesome feedback -- agreed on all counts! I expect performance and developer experience to evolve as points of competitive differentiation as we mature. We're still too early to make those claims defensibly.
ucarion 3y ago
You should check out Twenty! https://twenty.com/ https://twenty.com/ (YC S23) -- they're an OSS CRM. I totally agree the object management UI is too clunky right now. I want to redo that set of pages, they were the first ones we shipped. Not gonna lie, idk if anyone except me and Ned are really pining to learn hotkeys for managing object schemas, since in practice we're the only ones doing that on a regular basis -- we do initial setup on behalf of our customers. Yeah, I consider latency part of UX. We're doing some somewhat fancy stuff to reliably replicate every record into a couple of stores, each of which is optimized for different access patterns (search, get latest by ID, etc.). The big central Postgres(TM) is mostly there to be authoritative and to transactionally maintain invariants in the system.
- ensignavenger 3y ago
  Sounds like you guys have a great plan. I will check out Twenty, thanks!
- ctvo 3y ago
  > We're doing some somewhat fancy stuff to reliably replicate every record into a couple of stores, each of which is optimized for different access patterns (search, get latest by ID, etc.). The big central Postgres(TM) is mostly there to be authoritative and to transactionally maintain invariants in the system. When I, as a perspective customer, read things like this, it makes me question if I can trust you with my data or your platform long term. What is your technical expertise and what other similar systems have you built? I can’t seem to find it on the site.

noleary 3y ago

Awesome feedback -- agreed on all counts! I expect performance and developer experience to evolve as points of competitive differentiation as we mature. We're still too early to make those claims defensibly.

ucarion 3y ago

You should check out Twenty! https://twenty.com/ https://twenty.com/ (YC S23) -- they're an OSS CRM. I totally agree the object management UI is too clunky right now. I want to redo that set of pages, they were the first ones we shipped. Not gonna lie, idk if anyone except me and Ned are really pining to learn hotkeys for managing object schemas, since in practice we're the only ones doing that on a regular basis -- we do initial setup on behalf of our customers. Yeah, I consider latency part of UX. We're doing some somewhat fancy stuff to reliably replicate every record into a couple of stores, each of which is optimized for different access patterns (search, get latest by ID, etc.). The big central Postgres(TM) is mostly there to be authoritative and to transactionally maintain invariants in the system.

ensignavenger 3y ago
Sounds like you guys have a great plan. I will check out Twenty, thanks!
ctvo 3y ago
> We're doing some somewhat fancy stuff to reliably replicate every record into a couple of stores, each of which is optimized for different access patterns (search, get latest by ID, etc.). The big central Postgres(TM) is mostly there to be authoritative and to transactionally maintain invariants in the system. When I, as a perspective customer, read things like this, it makes me question if I can trust you with my data or your platform long term. What is your technical expertise and what other similar systems have you built? I can’t seem to find it on the site.