Good luck with this.<p>Some feedback is to work on update speeds. The docs mention 15/5 min updates, which is a shame especially working with gsheets.<p>Also - i looked at the pricing and its PER APP PER MONTH and also PER USERS (since u have to add 1000user packs). This can turn a simple corporate app into a $10K annual hosting bill.
I'm Sam, co-founder of Stacker. Since we launched on HN last summer (<a href="https://news.ycombinator.com/item?id=24037118" rel="nofollow">https://news.ycombinator.com/item?id=24037118</a>) and the batch ended, we've grown to be used in over 500 companies.<p>One of the key things we've realised from our customers that they've got a lot more data that what sits in their Airtable or Google Sheets. They all also use numerous SaaS tools that master different parts of their organizations' data: things like Stripe, Hubspot, Xero, Quickbooks and many more. They also sometimes have a production SQL database that contains critical customer information.<p>So we've been focused on expanding our product so we can incorporate more of our customers data and will be adding new data connectors through this quarter: we're starting with SQL, Stripe and Intercom. We want to enable anyone to snap their data together across whichever systems its stored in, and then create the most productive interface for them on top of it.
Great work! Some questions:<p>1. How would you compare Stacker to Retool?<p>2. Would the data from Stripe/Intercom appear as just another sheet/table?<p>3. One thing I learned that, despite the promises of no code solution, a non-technical user would still not use them, because they lack the know-how to model their domain knowledge in a no code tool. Have you run into these users? How would you work with them?
That's a name that took me by surprise, immediately reminding me of the stacker vs. doublespace lawsuits:<p><a href="https://en.wikipedia.org/wiki/Stac_Electronics" rel="nofollow">https://en.wikipedia.org/wiki/Stac_Electronics</a>
I'm sure this is reasonably good but I just can't help but think we've been here before with MS Access and then XAML .Net.<p>Maybe this time it'll stick.