Show HN: Selectable – mobile-friendly Postgres client
getselectable.com
getselectable.com
The key feature is the SQL query editor. The query editor was designed to be mobile-friendly. With autocomplete and a touch-friendly way to select parts of a SQL query, writing SQL statements with the query editor can - in some cases - be faster than typing the same query on a desktop.
The app supports the usual SQL client things:
- Browsing schemas, tables, and columns
- Running custom SQL statements
- Viewing results as a list, or as a table.
- Exporting results to CSV
- Saving queries (You can save one query in the free version)
The project is in very early stages, and is still missing a lot of features - notably the ability to insert, update, delete, or perform DDL via the query editor.
The app currently only supports Postgres, and is currently only available on Android.
Please give it a spin, and let me know if you have any feedback or feature requests.
Website: https://getselectable.com/
Play store: https://play.google.com/store/apps/details?id=net.weiyen.sel...
I'm not trying to replace desktops with mobile here. I think database administration is still going to be easier with a big monitor and a keyboard, and that's not going to change.
Rather I'm trying to open up database administration to people who don't have desktops, or who are more comfortable working on their phones.
Looks like very nice UI model, it’s not an easy problem to solve. Also one of the few times a portrait YT video is wholly appropriate.
With the tri-fold mobiles and Samsung Dex like feature coming, that day may not be far when mobile become the single work machine.
Sadly this specific app doesn't seem very polished or useful.
- When in the table explorer it's odd that the primary action - viewing a table - is behind a dropdown menu. maybe clicking the table name opens the browse rows screen and clicking a column opens with a select prefilled.
- Please default to a limit 500 or something like Jetbrains to prevent me making stupid mistakes.
For professional use cases, maybe if you're on call and need to access the DB over your phone (though I hope I'm never in that spot). Having documentation around network model - do you relay queries through your own backend - and the security model for data and credentials. Do you support any secure connection methods, like SSH tunnel, or does the PG need to be facing the public internet?
You could also hide it behind tailscale/nebula or some other VPN thing.
public key cryptography is well understood and used everywhere: HTTPS, SSH, Signal, etc.
See: https://en.wikipedia.org/wiki/Public-key_cryptography
In postgres specifically: https://www.postgresql.org/docs/16/ssl-tcp.html and https://www.postgresql.org/docs/16/runtime-config-connection...
You can enforce TLSv1.3 on all network connections using `ssl_min_protocol_version`(postgres.conf) and `hostssl`(in pg_hba.conf)
This puts you ahead of most web servers which often still allow TLSv1.1.
You can make Postgres secure or not, your call. Just like with everything else.
The process starts with a client and server hello. Then the server sends its certificate to the client, and the client sends its certificate to the server. The server verifies that the client’s certificate is signed by a certificate authority in its trust store. That’s the authentication part. The client’s private key is not used.
The confidentiality comes next if authentication is successful.
I asked because X509 certificates are complex and difficult to securely parse. Also mTLS is rarely used.
> The client’s private key is not used.
This whole section is incorrect. It's called mutual TLS. The client's private key is used to prove to the server it has the private key for the public key it's handing to the server. Just like the server has to prove to the client, it has the private key to the public cert it hands out.
Otherwise there is no authentication going on at all.
See the RFC: https://www.rfc-editor.org/rfc/rfc8446 If you are unfamiliar with RFC's, see Section 4.4 and Appendix E.1, which talk about client auth and the handshake respectively.
> I asked because X509 certificates are complex and difficult to securely parse
Yes, but that's why PG relies on OpenSSL to do that work for them. It's widely deployed, even using client certificates. X.509 is used with client certificates by at least 3.5M active personnel with the US DoD via their Common Access Card, as one widely used example.
> Also mTLS is rarely used.
Mutual TLS or client auth is not often used in the browser context, because the browsers have miserable UX around it. I wish that would change, but I'm one of the very few.
It's regularly used outside of the browser context though. Lots of B2B and Service Oriented Architectures use it.
Without that there is still authentication: clients who don’t presents a certificate signed by CA are refused. A weaker form of authentication is who ever presents a signed certificate connects, regardless of whether they hold the private key or not. In practice, these two are packed into a p12 certificate anyways, at least browsers.
Interesting that defense industry uses mTLS. It’s a pitty because the UX could be good: no need to route the entire traffic by a VPN. Simply have a certificate in the browser and the user will have access with no further action or setup.
I did not know about wasm-postgres, thanks!
> Having documentation around network model - do you relay queries through your own backend - and the security model for data and credentials. Do you support any secure connection methods, like SSH tunnel, or does the PG need to be facing the public internet?
There's no backend, the app opens a connection directly to the database. Credentials are stored on-device. No data will ever be shipped to a third-party without user consent, and I will never change this. (This is a large part of why I haven't put in any "AI" features yet.)
The app currently does not support SSH tunneling. This is something I will be working on soon.
Also fair point on the documentation. There's currently 0 docs around the app, and I'm not proud of that.
Fancy seeing a full-blown mobile Postgres editor. I can definitely see a few use cases but I'm curious whether your average Db admin or data engineer will be interested in using a tool like this.
I wonder what other apps are just RDB wrappers that could almost be substituted with something like this.
Thanks for sharing!
Also, several Postgres providers now also provide a SQL editor / runner and table visualizer in their UI.
What do Postgres users here think is the biggest missing thing in current clients? Are they too heavyweight? Too generic and don't support advanced Postgres features? Don't look modern enough? Not mobile friendly? Or is it something else?
i.e. maybe there could be a searchable list of common sql solutions and then somehow adjust that to suit the actual problem (hopefully without ending up a cluttered mess of sql)
This is a good idea, thanks for the feedback!
Add an AI query tool - you could do it on-device with something like functionary ggml and llama cpp with a few functions:
getSchemaForTables(...) getTableStats() runQuery('...')
Then you could do a query like:
"show me all customers who regularly post between midnight and 1am"
From my understanding, usable on-device LLM models tend to be gigabytes-large, which makes it difficult to roll out to everyone. Apple Intelligence might make this feasible, will need to do more research on this when I do the iOS port.
Making AI an optional add-on might be doable.
Thanks for the feedback!
So in my king there is a brief spark of "why does this site want to make me selectable?"
One saved query is super restrictive though, basically means either pay, or don't even bother to install.
Re. the saved query restriction - I am planning to work on this app in the long term, which unfortunately means I have to monetise the app in order to sustain development work.
I believe restricting saved queries and saved connections is a good compromise to allow casual users to try out all the features the app has to offer, without imposing a time limit.