framelesshelper VS ExtPay

Overall, I love Qt. I started studying QML 2 weeks ago to implement a Kanban view based on the underlined Markdown styled todo items in the text editor, and it's been really great so far. Property bindings, signals & slots, integration with C++, it all makes so much sense, much more than other declarative languages/frameworks (looking at you, React) imo.

Qt has been around for years, the documentation is extensive and the community is large and supportive. With QML I faced many problems, especially half-assed examples/documentation, Qt Creator's intellisense doesn't work well with QML sometimes, etc... But the tradeoff is worth it. I'm getting things done in a much faster pace with QML.

A problem that is common both in Qt and other cross-platform frameworks is that you end up writing some custom code for each operating system to make the look and feel more native. But I think it's getting better with awesome open-source projects taking care of beautiful native window decorations[1].

[1] https://github.com/wangwenx190/framelesshelper

Love what I see here. This could possibly work perfectly together with FramelessHelper (github.com/wangwenx190/framelesshelper) which I use in my own application.

I evaluated first because I wanted to achieve a true frameless window styling which is way harder to do in widgets than in QML. I stumbled upon FramelessHelper (https://github.com/wangwenx190/framelesshelper) then (which is also available for QML) and I started in widgets. It fully depends on what you like more. I am still not a fan of writing JavaScript for desktop applications (except extensions) and since I've started with Qt I always used Widgets. I just feel more home on this side.

I've been using SQLite/Litestream for https://extensionpay.com for about 3 years now! Serves about 120m requests per month (most of those are cached and don't hit the db), but it's been great!

I was convinced that SQLite could be a viable db option from this great post about it called Consider SQLite: https://blog.wesleyac.com/posts/consider-sqlite

Using SQLite with Litestream helped me to launch the site quickly without having to pay for or configure/manage a db server, especially when I didn't know if the site would make any money and didn't have any personal experience with running production databases. Litestream streams to blackblaze b2 for literally $0 per month which is great. I already had a backblaze account for personal backups and it was easy to just add b2 storage. I've never had to restore from backup so far.

There's a pleasing operational simplicity in this setup — one $14 DigitalOcean droplet serves my entire app (single-threaded still!) and it's been easy to scale vertically by just upgrading the server to the next tier when I started pushing the limits of a droplet (or doing some obvious SQLite config optimizations). DigitalOcean's "premium" intel and amd droplets use NVMe drives which seem to be especially good with SQLite.

One downside of using SQLite is that there's just not as much community knowledge about using and tuning it for web applications. For example, I'm using it with SvelteKit and there's not much written online about deploying multi-threaded SvelteKit apps with SQLite. Also, not many example configs to learn from. By far the biggest performance improvement I found was turning on memory mapping for SQLite.

I made a couple browser extensions that make over $500/month each. The key seems to be naming your extension after high-volume search terms and getting good reviews on the chrome store (and obviously having an extension that works well and solve a common problem on major websites). I monetized them with my own service, https://extensionpay.com. Feels so good to eat your own dog food :)

Neat! I'm serving around 120m requests per month for https://extensionpay.com from a 2GB VPS running a single-threaded nodejs process and SQLite as the db. Most of the requests are cached, but still, it's amazing how far you can get with cheap hardware.

I use SQLite/Litestream for https://extensionpay.com! Serves about 120m requests per month (most of those are cached and don't hit the db), but it's been great!

I have no affiliation with Litestream but I was convinced that SQLite could be a viable db option from this great post about it called Consider SQLite: https://blog.wesleyac.com/posts/consider-sqlite

Using SQLite with Litestream helped me to launch the site quickly without having to pay for or configure/manage a db server, especially when I didn't know if the site would make any money and didn't have any personal experience with running production databases. Litestream streams to blackblaze b2 for literally $0 per month which is great. I already had a backblaze account for personal backups and it was easy to just add b2 storage. I've never had to restore from backup so far.

There's a pleasing operational simplicity in this setup — one $14 DigitalOcean droplet serves my entire app (single-threaded still!) and it's been easy to scale vertically by just upgrading the server to the next tier when I started pushing the limits of a droplet. DigitalOcean's "premium" intel and amd droplets use NVMe drives which seem to be especially good with SQLite.

One downside of using SQLite is that there's just not as much community knowledge about using and tuning it for web applications. For example, I'm using it with SvelteKit and there's not much written online about deploying multi-threaded SvelteKit apps with SQLite. Also, not many example configs to learn from. By far the biggest performance improvement I found was turning on memory mapping for SQLite.

Happy to answer any questions you might have!

I made https://extensionpay.com to monetize my own browser extensions and between that and free distribution on the extension stores it’s really easy to try making extensions that make money. So far devs have made over $300k with ExtensionPay. That said, it still take some skill to find a niche that works.

Just want to put a plug in for https://extensionpay.com/ - I've used it in extensions in the past. It takes away the headache of setting up a backend for payment. They do take an extra 5%, but it's worth it especially. for smaller projects

Have a go at looking at this: https://extensionpay.com,

That's fair. Right now my payment processor (ExtensionPay) doesn't support multiple pricing tiers. However, in the future I'm considering rolling out my own logic so that I can provide a lifetime license option for some users.

Oh nice! Maybe you'd be interested in the tool I built to take payments in extensions: https://extensionpay.com

If your concern is about security of the extension, you may right click on top of the extension's icon and select "Inspect popup". Select the "Network" tab and type CTRL-R to force a reload of the extension. Verify there are no external network requests (except to extensionpay.com for paid features).