• 1 Post
  • 5 Comments
Joined 3 months ago
cake
Cake day: October 28th, 2024

help-circle

  • I really appreciate you taking the time to share your thoughts so candidly. No worries at all - your feedback isn’t rude! If anything, it’s incredibly helpful in understanding how the messaging comes across to users, and that’s exactly the kind of insight we need to improve.

    I totally get where you’re coming from with the SSO concern. Even if it’s more of a personal preference, it’s still a valid point, and I respect that. We’ll definitely consider adding a simple email-based sign-up option to give users more choice.

    As for the Mac-only part, I hear you loud and clear. It’s frustrating when you’re excited about something, only to find out it’s not available on your platform. That’s on us for not making it clearer upfront, and we’ll be adjusting how we communicate this in the future to avoid any confusion.

    On the ‘ChartDB 2.0’ vs. ‘Buckle’ transition - I get why this felt misleading, and I appreciate you calling it out. Our intention wasn’t to do a bait-and-switch, but I can see how it might have come across that way. The goal was to show continuity between ChartDB and what we’re building next, but we’ll rethink how we present this so it’s clearer from the start.

    I really appreciate you sharing your perspective, and I hope you’ll keep giving us this kind of honest feedback. It helps us make things better for everyone. Thanks again!

    Cheers, Jonathan


  • Thanks for your detailed feedback! I really appreciate you taking the time to share both your concerns and what you like about ChartDB. Let me address each of your points:

    ChartDB v2.0 & Mac-Only Availability - I completely understand your frustration. We should have made it clearer upfront that the initial release of ChartDB v2.0 (Buckle) would be Mac-only. The reason behind this decision is that we’re prioritizing a solid foundation on one platform before expanding to Windows and Linux. That said, we’re actively working on cross-platform support, and I’ll make sure we communicate this more transparently moving forward.

    Clarity & Messaging Around ChartDB v2.0 - You’re absolutely right that the messaging around ChartDB v2.0 could be clearer and less intrusive. We’ve received similar feedback and are actively working to improve this experience. You can track the updates and contribute to the discussion here: GitHub Issue #541. We want to ensure that users get the right information upfront without feeling pressured or misled.

    The Name ‘Buckle’ & Product Direction - Buckle is our next-gen database tool, built on the foundations of ChartDB but designed to be much more interactive and powerful. The reason for the new name is that it’s not just an update—it’s a complete reimagination of how database tools should work. But we should definitely make that distinction clearer so users know what to expect before signing up. And yes, we’re exploring a freemium model to keep the core experience free while offering advanced features for those who need them.

    Third-Party Sign-Up - I hear you on this! The reason we ask for sign-in via Google/GitHub is to prevent spam and ensure a smooth experience when we roll out access. We also only request the minimal permissions—just your email and name via SSO. It’s not full access to your Google or GitHub account, and we don’t retrieve any additional data. That said, I understand that some users may prefer a simple email-only sign-up, and we’ll consider adding that option in the future.

    Feature Requests (Adding Views & VARCHAR Length) - I love that you’re thinking about these details! Right now, ChartDB shows existing views but doesn’t support adding new ones directly. We definitely want to include this in the future, as it would make the tool much more useful for database design. As for setting VARCHAR length - great catch!

    We currently don’t expose that option, but it’s something we’ll look into adding. I truly appreciate your honest feedback. It helps us improve and make ChartDB/Buckle a better experience for everyone. If you have any more suggestions or need clarifications, I’d love to hear them! 😊