tonyx

This is really cool. How do you handle changes of pricing with something like this?

Interesting! Is there an escape hatch to drop down to raw Stripe primitives if someone needs a feature you haven’t modeled yet?

This feels like something many teams eventually build internally — curious how you’re thinking about long-term API surface + compatibility with new Stripe features.

How does this compare to other open source integration platforms like Nango or Airbyte?

Can you comment on cells and rows ? Document columns?

Congrats on the launch!!

if it's postgres, then 5 mins as shown in the video :) Otherwise what data warehouse are you thinking of and what's the use case behind it?

Can you clarify what you mean by "not out of box" API? We haven't built an integration with Argyle yet but once we do it would be the same experience as Plaid

This is a lesson that needs to be learnt and relearnt over and over again, with increasing level of clarity each time.

The largest size we tested was 150mb, that's why the x-axis of the graph ends at that point :)

Impact can exist regardless of the underlying cause for impact. It may be because someone's device is full, or does not want to download over cellular, or any other myriad of factors. But you'll still lose an install statistically speaking.

@CharlesW we mostly focused on the facts and running as controlled of an experiment as possible without bias or drawing conclusion on exactly why heavier apps get downloaded less. Though my personal guess from working years in the mobile app space is that users are surprisingly conscious of data & disk usage. Not everyone has unlimited data or 128GB storage iPhones.