Show HN: Base, an SQLite database editor for macOS

The Hacker News discussion about the application "Base" for SQLite reveals several key themes and opinions from users.

Native macOS Experience and User Interface

A strong recurring theme is the appreciation for Base's native macOS look, feel, and behavior. Users contrast this with cross-platform toolkits that may not fully capture the nuances of the macOS environment.

• "Base is nicely done, I’ve found it worthwhile over other options." - WhitneyLand
• "It fits with the system better and behaves more like other macOS apps" - __bb
• "There’s a truckload of little things that native AppKit apps get you that nothing else will, not even other “native” toolkits like Qt. Things like Option-clicking a disclosure triangle in a nested list expanding/collapsing all children recursively, which one comes to use frequently and misses when absent." - cosmic_cheese
• "A nicer user interface." - jen20
• "Polish and decent UI..." - vsl
• "I like these kinds of things though. Minimal purpose built tools." - reactordev

This focus on a polished and native experience is seen as a significant advantage, even if it limits the application to macOS.

Comparison with Existing Tools (SQLite Browser, DBeaver, TablePlus, etc.)

Users frequently compare Base to other popular SQLite or multi-database tools. The discussion highlights perceived shortcomings in other tools and identifies Base's differentiators.

• "I've been using DBeaver, but it's not optimized for SQLite. Common issue with DBeaver is having to refresh the global connection to see changes." - nodesocket
• "What does this offer over sqlitebrowser?" - packetlost
• "sqlitebrowser is 100% open source, cross platform and free. I don't think Base is at all and only supports macOS" - colesantiago
• "I find the sqlitebrowser UI to be perfectly fine. It's not pretty, but it's a tool so who cares." - packetlost
• "I've been using TablePlus a lot, but there are some SQLite-specific features I'd really like to have in an app: - Foreign keys enabled by default, so I don't have to remember to enable that in every session." - markusw
• "mastermage: Wait doesnt DBeaver work on MacOS aswell?"
• "weaksauce: not as slick as this tool but https://dbeaver.io/ handles duckdb databases as well as a myriad of others."

The primary advantages cited for Base over alternatives like SQLite Browser include a more aesthetically pleasing and functional user interface, better integration with macOS features, and specific SQLite optimizations.

Target Audience and Use Cases

There's a discussion about who Base is for, with many users clarifying that it's beneficial not just for hardcore developers but also for a broader audience. Utility for data analysis, prototyping, and interacting with data from other applications are frequently mentioned.

• "I find myself always needing to query SQLite databases from applications like games, phone backups, or even custom apps that I am testing. GUIs are very convenient to explore and play with the databases." - jraph
• "A lot of people use it as a step up from Excel. I’ve got quite a few scientists using it for data analysis, a whole bunch of people importing sales data for querying. A good number of folks never write any SQL and just use the GUI to sort/filter data." - __bb
• "I know researchers (think field biology) who need to enter data into SQLite databases with bespoke apps but on occasion it’s imperative to edit or search the database directly. I’ve helped them do that on some butt-ugly app they had installed whose name escapes me. Looking at Base, my immediate thought was to buy it for them." - latexr
• "It's for manipulating SQLite databases with a GUI, rather than in a web page or at the command line. I previously used V2 of Base and the user interface was excellent, and this looks to be even better." - msephton
• "1. If you're a developer, then you're probably using sqlite to store data and having a GUI for checking/modifying the database is probably handy. 2. Most application by other developers (even massive companies) use sqlite to store data under the hood even if the file doesn't appear to be named .sqlite. So if you want to tweak certain settings that aren't exposed to the end user, then you can use this to do that in a more user friendly way rather than crack out a command line tool for sqlite changes." - xmprt
• "Storing results for scientific research - Local analysis of data exported from server-based databases - Experimenting with database designs before exporting SQL to codebases - Maintaining relational data where a website or app are not needed (eg. tutors keeping client records) - Recovering data from databases used by other products (eg. phone backups, discontinued apps)" - __bb
• "It would be so much better if he could store these things in SQL - for non developers, they often use Excel, when a SQL DB is the correct solution, just because they can't figure out SQL at all. A visual editor/manager is perfect for them - create a table with columns, enter data, later integrate with other tools that can pull it out." - citrusybread
• "While I know my way around and even enjoy the command-line, on occasion I bump into some app’s SQLite database that I want to explore. I can see myself using a GUI for those instances to help me find the data I’m looking for faster." - latexr

The general consensus is that while a command-line interface is powerful, a GUI provides significant convenience for exploration, data manipulation, and for users less comfortable with SQL.

Longevity and Developer Support

Several comments highlight the long-standing nature of the application and express appreciation for the developer's sustained effort and responsiveness.

• "Happy Base user for almost ten years now. Hands down the best SQLite editor on macOS." - janten
• "I've been using Base for [checks... considers retirement] about 15 years!? It's ALWAYS been great, AND has improved over time." - thomasqbrady
• "__bb: Thank you for the support! It means a lot."
• "__bb: Thank you for the support :)" - __bb (responding to wulfstan from 2010)
• "I bought your app in 2010 and use it regularly. Thanks for making it!" - wulfstan

This longevity suggests a reliable and well-supported product. The developer's active participation in the thread, answering questions and acknowledging feedback, is also positively received.

Platform Specificity (macOS Only)

The fact that Base is exclusively for macOS is a point of discussion, with some users expressing a desire for cross-platform availability and others defending the choice to focus on a native macOS experience.

• "TheJoeMan: May I ask what you are using on the backend for verifying the web purchases? Is it a key, or online activation once downloaded?"
• "__bb: I use Paddle (https://paddle.com/) as merchant of record because I don't want to deal with the paperwork of doing more myself. In practical terms, it's a key emailed after purchase."
• "TheRealPomax: Why is it MacOS only though? Surely this can cross-compile for Linux and Windows perfectly fine?"
• "jen20: Probably because it’s written using native Mac UI instead of half-assed with electron."
• "hoistbypetard: Because it a GUI that uses Mac-specific UI libraries that aren't available on Linux and Windows?"
• "This is why it is macOS only. Because it’s written using AppKit and SwiftUI, which are only available for macOS. This makes for a much nicer app for Mac users, even if it does cut your potential audience." - __bb
• "Too bad this is mac only. I mean, im a mac user (among other things) but i don't want to depend on platform specific tooling." - klabb3
• "daneel_w: Disappointed to see it's built with macOS 15.0 as minimum target."
• "__bb: Because I don't have the capacity for maintaining compatibility between too many versions of macOS. For v3, I've stated the goal - not guarantee - of supporting the current and previous versions of macOS."

The developer explains this choice is due to the use of macOS-specific UI frameworks (AppKit, SwiftUI) and a desire to maintain a high-quality, native experience, managing their development capacity.

Feature Set and Scope (Avoiding Bloat)

Users and the developer discuss the intentional design choice to keep Base focused on SQLite and avoid turning it into an all-encompassing IDE or a feature-rich application like Microsoft Access.

• "The goal of this app is to provide a comfortable native GUI for SQLite, without it turning into a massive IDE-style app" - reaperducer quoting the app's description.
• "feature bloat is a massive problem with macOS database tools. I'd happily pay for something basic, native, and pretty like Sequel Ace†, but all of the other options are Swiss Army knives for power users who need to tweak every little thing. I just want to do some queries." - reaperducer
• "criddell: > without it turning into a massive IDE-style app Is that another way of saying you don't want to make MS Access?"
• "__bb: Sort of, yes. But mostly that I don't want the app to become the "everything to everyone" style of editor. I want it to remain tightly focused on the features that SQLite provides. It's unlikely that I'll add a form builder or report generator to the app. I don't want it to grow until it can send email."

This philosophy is met with approval, as users appreciate a tool that excels at its core purpose without unnecessary complexity.

Payment and Distribution Model

The discussion touches upon the application's distribution channels and pricing, including direct sales and the Mac App Store, as well as the decision not to offer an upgrade price for existing users.

• "vahid4m: Does apple allow you to to sell both through App Store and direct through another payment echo system? I thought they are more strict than that."
• "__bb: Yes, it's OK to do that, but not to cross the streams. You can't advertise direct purchases from the Mac App Store version."
• "dlachausse: I see that this software is available for direct sale, the Mac App Store, and through Set App. What is your revenue breakdown from each if you don’t mind sharing?"
• "__bb: It's a bit too soon to tell reliably, since I've shipped v3 as a new app and it hasn't settled down yet. For v2 it used to be 60% App Store and the remainder direct/Setapp. So far for v3 it is approximately 60% direct, 25% App Store and 15% Setapp."
• "joao: Customer here, from previous versions. Could you expand on the reasoning of not offering an upgrade price? Is it just to messy nowadays on the technical side, especially with the Mac App Store? Will be upgrading in the future, congratulations on the launch!"
• "__bb: There’s two main reasons. One is that this is the first paid update in 14 years. The second is that it’s just such a pain to do that on the App Store and I don’t want to have a two-tier system. I’ve tried to strike a balance on the price bearing this in mind."
• "sneak: Thank you for offering a purchase option outside of the MAS. It sucks that Apple is trying to force everyone to identify themselves to install apps and some of us prefer not having an Apple ID."
• "aaomidi: It's crazy how expensive these small utilities are. And worse, because they're paid you don't even get the source code to fix issues yourself :/"

The developer explains the complexities of managing multiple distribution channels and the historical context of pricing, noting the first paid update in 14 years. The option for direct purchase is appreciated by users who prefer to avoid the Mac App Store.

Specific Feature Requests and Technical Details

Users propose specific features and raise technical questions, such as support for SQLCipher, auto-loading extensions, UUID handling, and collaboration.

• "However Base doesn’t (currently) have support for SQLCipher." - __bb
• "markusw: Auto-enabling foreign keys absolutely should be an option. I'll make a note of it. I don't know about auto-loading extensions though. Will look into it. That might not mix well with the App Store rules and I'm reluctant to let the direct/app store versions drift apart in terms of features." - __bb
• "It would be amazing if it could display UUIDs. SQlite doesn't support them natively, but many people store them as binary blobs. Jetbrains products realize that these binary values are UUIDs and let me edit them easily." - earthnail
• "klabb3: Too bad this is mac only. I mean, im a mac user (among other things) but i don't want to depend on platform specific tooling."
• "da_chicken: See, I would be terrified of doing that because different RDBMSs and languages store and sort UUIDs differently. A UUID is not just a number. It's a structured data format."
• "tsp: Would be cool if this could connect to Cloudflare SQLite DBs."
• "alifatisk: I am thinking of an application where multiple users can interactive with the workbench BUT the workbench performs its actions against the database as one user. That way, it could consolidate the connections into a single one"
• "jen20: In other words, a database server around Sqlite? That seems like the kind of thing that should exist!"
• "__bb: I realise you’ve hinted at it, but also think it’s worth explicitly pointing out that it’s more about the number of users writing than just user count. It can handle concurrent readers with little bother."

These discussions indicate areas for potential future development and highlight specific user needs.