4 ms·
Hey Matt, Your product fits perfectly a feature we're building and we'd love to use it. But it needs to be programmatically accessible in react (js lib) and of
by username_my1 4y ago
Hey Matt,
Your product fits perfectly a feature we're building and we'd love to use it.
But it needs to be programmatically accessible in react (js lib)
and of course it needs to function very smoothly with large number of events.
Good luck going full time I see a need in this exact space !
- matt1 4y agoThere's no API at the moment to programmatically build your timeline, but that might be something I add down the road. Here's the relevant post on Preceden's public roadmap if you care to give it an upvote: https://roadmap.preceden.com/b/y0ge5xve/feature-ideas/api https://roadmap.preceden.com/b/y0ge5xve/feature-ideas/api Hope it winds up being a good fit even without an API.
- username_my1 4y agoalready upvoted it. unfortunately it won't work without the APIs because it needs to be part of our product and there the data is constantly being updated dynamically by different actors / processes .
- matt1 4y agoNoted - thanks for the nudge to work on it!
- jimnotgym 4y agoHey Matt, I can't develop cool looking apps like this. I'm envious. What I can tell you is that sales people at big software companies never say 'No it can't do that' as an initial conversation. They would say something like, 'I'm sure it could do that. Let's set up a call to get your requirements straight'. He might only need a subset of your features, and the api needed could be trivial. He might have a $moneyisnoobject Corp waiting to pay. I mean you are completely within your rights to push away non-core users if you want.... but you know when a saas price page has Free, Basic and Enterprise teirs, and the Enterprise one has 'please call' next to it? That is because the price for customization is too embarrassing for both parties to make public!
- matt1 4y agoGreat points - thanks for suggesting that approach!