[christophepas]

Thanks for sharing! What was inferior about Slite (and when did you use it)?

I’m working on it, would love to hear your takes, especially as in term of performance and speed we worked heavily this year and believe to have reached something superior to alternatives.

[steve_adams_86]

I used it about 1.5 years ago.

I wish I had access to the issues I was going back and forth with your team on, but I no longer have access to that email account.

One big thing we wanted was relationships. Perhaps we’d keep data in a table and some entries would link to another document. At the time, this wasn’t possible but I was told it was on the horizon/being considered.

Otherwise we had issues with performance slow downs when we allowed documents to get very large. This was generally bearable, but we had some documents we didn’t want to break apart (for reasons), and opening them up became a little frustrating. They didn’t scroll well and editing them was laggy, for example.

I trust your team has been working hard on it because it was very evident that the team cared a lot and was super attentive. I constantly worried I was being annoying, but I got quick, steady, and very gracious responses, always looking to provide useful information. Super positive experience in that regard!

[steve_adams_86]

I can't edit this now, but it just occurred to me that the relational data issue was specific to Slite, not Notion. Racking my brain, I'm fairly sure the issue we had most with Notion was performance.

[christophepas]

Super clear and useful!

The performance definitely is something we improved a lot, and indeed relational data - I guess you mean roll ups in database- is not something we allow at the moment, thanks for sharing again!