Verified purchaser
Not Quite There Yet For Me
First, the positives,
1.) Support is quick to respond to questions.
2.) The API feature has the potential to be a huge timesaver.
Now, the not so positives,
1.) I reached out a week ago about an issue with the LinkedIn API not pulling in data and haven't heard back from anyone yet. It's still not working for me.
2.) It's clunky when it comes to linked fields. You can double click or press Enter twice to open the rows; however you have to click the save button with your mouse to move to the next field. That makes it tough to find a flow, especially for those of us who would prefer to do everything from our keyboard.
3.) It's not the fastest. I have 6 stacks and neither have more than 50 rows of data each; however, when I switch to a new tab in a stack, Stackby needs time to "think." Granted, it isn't a long time but I'm concerned what this would look like with 5K rows and 10+ stacks.
4.) History - With the LTD, we are supposed to be able to see 3 months of history. When expanding the row, I don't see history on any row, in any stack. When clicking the history feature in the header bar, it says that to use Stack Snapshot, you have to enable Powerups (more on this in a bit). Seeing history is important (even if it's only 3 months of history), especially when using APIs. For example, when I click on my LinkedIn table, I can see that 64 API requests have been submitted; however, I have zero data in my stack. Without being able to view history, I am unable to verify that my other APIs are working as expected.
5.) Powerups are $79. If I didn't have concerns, I'd spend the $79 to unlock additional features. Right now, I'm just not comfortable doing so.
6.) Last but not least, templates . . . they are great for ideas; however, I'd suggest building a stack based on the template. The auto-numbering feature doesn't reset and once data is added to edited columns, each row seems to need to be relinked by expanding the row. By recreating the stack, you may spend more time initially, but it may save time in the longrun (and possibly even prevent errors because you think something is linked when it isn't).
With all that being said, I do think Stackby has a lot of potential. It's just not there yet for me, especially not to use with multiple members of a team. Since there is an import feature, I may keep Stackby and see how things progress. Hopefully, Airtable will be added to the import options at some point. Glad everyone else has had a really positive experience with it.
Rachit_Stackby
May 9, 2024Thanks for the review.
1. For LinkedIn API, there have been some changes from LinkedIn's side and we're working with their team to get this sorted. We're still waiting to hear back from them. As soon as it's done, the issue will be resolved.
2. For Linked fields, I've taken your feedback and we will improve the double click and tab movement features on our expand model for linked rows. You will see the improvements in the coming week. Wish we knew this earlier!
3. We're solving for performance on day 1. Please test it at 50K rows and 50 stacks :) We're constantly striving to get better here.
4. For History, today we're not saving information on when you called that API but all the cell level information is stored on individual row. I've taken a note of this and we'll add additional tags in the history on when the API was called. Because LinkedIn API was not working on your end, it led to this.
5. Ok
6. Auto-number does not update after you delete rows. It takes from the last row. That's actually done by default since different users have different expectations on how it should behave. We can infact give an additional toggle to make allow for both. So you will see improvements in the near future.
Our goal is to make this review 3 tacos to 5 tacos as soon as possible and onboard you with your whole team to Stackby :)
Please wait for our email with the changes you mentioned.