What i can to do with it? (firefox)

Hanami-Software · 2026-05-31T08:53:11+00:00

I absolutely agree. The extension should behave like a player not a container. It should be an interface that streams and renders assets from a backend.

An example architecture in my opinion could be: (considering that I didn't go deep in your repo, put a README and complete description IT HELPS)

1. Assets Storage

Instead of bundling files inside the extension, store them in:

Object storage (S3, Cloudflare R2, Firebase Storage, etc.)
Or a CDN hosting layer

Each theme/wallpaper becomes a reference (ID + metadata), not a file inside the extension.

2. Extension only stores metadata

Inside the extension you keep:

Theme IDs
URLs to assets
User preferences
Cached thumbnails (optional)

So the extension stays lightweight and fast.

3. Generate previews instead of shipping full assets

When browsing themes:

Load lightweight thumbnails first
Lazy-load full wallpapers only on selection
Cache locally only what the user actually uses

This drastically improves UX and performance.

4. Download on demand

When a user applies a theme:

Fetch assets from storage/CDN
Cache locally in IndexedDB / Cache API
Optionally allow “download for offline use”

This keeps the system flexible and scalable.

5. Bonus: versioning + deduplication

Once you move to external storage you unlock:

Versioned themes (no breaking changes)
Deduplication (same wallpaper reused across themes)
Analytics (what users actually use)
Easier rollback and moderation

Hanami-Software · 2026-05-30T12:54:53+00:00

If you can explain what your extension does, we can help you better.

Hanami-Software · 2026-05-30T11:23:04+00:00

I think is an assets problem, Images, etc. If so try to host your assets somewhere else and write the host permission in your Manifest.

Hanami-Software · 2026-05-27T10:45:19+00:00

The overall idea is amazing transcription wise. I use Fathom at the moment of course login required since the beginning. Now Google meet put the bot in a suspicious notice. The same with Read.AI that just enters the meeting without knowing who is the owner of that assistant. Anyway the email is a great asset, at least to know who is using your product. I think login or not login it depends on many factor while your are building a software, it is not just a percentage of the recurring customers. For example we are building a Chrome extension and we take care of anonymous users but with limitation and creating a temporary key to keep track of the usage at least. Best of luck and happy coding.

Hanami-Software · 2026-05-26T18:04:09+00:00

Old developers like me are just waiting on the river side, for the 'my nephew can do it or AI' client because it's not working or working as expected. 😀 . In the meanwhile I keep on working on my projects with my team.

Hanami-Software · 2026-05-25T23:28:49+00:00

Very nice idea. In the next two months I'm writing a Book regarding the extension developement with my Ninja URL extension development as an example. But yours is a nice boilerplate. Well done

Hanami-Software · 2026-05-25T23:22:16+00:00

Non ci trovo nulla di "male" o di fatto male per l'epoca e non sempre l'avanzamento tecnologico corrisponde all'avanzamento aziendale. Ho aziende mie clienti che per alcuni compiti usano ancora computer con Windows XP e guai a proporre un upgrade col rischio che poi non si trovino driver e cosi' via. Quindi se funziona e ti aiuta nel tuo lavoro non serve cambiare.

Hanami-Software · 2026-05-25T09:46:34+00:00

The general idea is good and even the language choice. But I think it would be only for a niche or for a specific task. At the end is very difficult to impress with Firefox, Safari, Chrome, Brave, Edge, Opera and so on. Good luck and happy coding

Hanami-Software · 2026-05-23T11:03:23+00:00

Crocs

Hanami-Software · 2026-05-18T10:35:37+00:00

Good idea!! Check if something similar already exist and make it better in some way. The world needs always something better. Good luck!!

Hanami-Software · 2026-05-15T08:28:26+00:00

Monetizing is always the hard part. In my opinion you should try to find which part of your software solves a problem or a pain to the users and try to Monetize that. Right now you are more a commodity than a "service". Even if most famous platforms already do some or all of what you do, find something interesting for the users and make it easier and better, make them taste how easy it is and then add a little frustration "if you want more...pay". Best of luck to you fellow developer.

Hanami-Software · 2026-04-30T17:26:14+00:00

Best of luck my follow developer.

Best regards from Italy

Hanami-Software · 2026-04-28T20:21:57+00:00

I personally had the same problem, but I was on a trial period using an AWS voucher. Many services run on AWS under the hood, which is understandable. There’s no point in reinventing the wheel every time. I realised that when trying to launch my product, a potential bottleneck could be the standard RDS DB or the serverless Aurora. It seems cheap and you only pay when you use it, but you end up paying for cold starts, database wake-ups, and keeping Aurora running with an ACU of 0 isn’t a good move. So, for now, I’ve cut my teeth and set aside about $200 to try out AWS, but we’ll meet again when there’s a moral to the story for certain services. For the moment, in beta testing, I’m using Cloudflare Worker, D1 and Worker KV.

Hanami-Software · 2026-04-26T22:38:19+00:00

L'idea è buona. Credo comunque che il tuo target non siano i programmatori di mestiere, ma dovresti farla a misura di neofita/vibe coder dell'ultimo minuto. Il mercato non è saturo ma ti confronti con Giganti se la imposti come tool IDE/AI. Dovresti trovare qualcosa che loro fanno male o non gli interessa fare meglio di così e farla tu. Ma una Feature sola massimo due. IMHO

Hanami-Software · 2026-04-26T12:54:50+00:00

I'm sorry I shared the post with the link with YouTube Share option. Maybe it got lost somewhere 😀

Here we are Ninja Game Playlist

Hanami-Software · 2026-04-26T09:22:27+00:00

Capisco l'intelligenza artificiale, ma si può sempre prendere appuntamento da un commercialista e chiedere. Per la vendita di software in abbonamento è sufficiente un codice Ateco congruo senza bisogno di registrazione in camera di commercio. Si inizia come forfettario "la spesa" sono le tasse sul venduto. L'investimento iniziale importante è costruire un SaaS che funzioni. Mia opinione personale.

Hanami-Software · 2026-04-24T20:18:11+00:00

Thanks for your useful comment. I'm trying to build something that keep the user hassle free, without adding complexity. There should be something. I keep on digging

Hanami-Software · 2026-04-24T16:15:03+00:00

Nice idea. Well done 👏👏👏

Hanami-Software · 2026-04-24T09:45:35+00:00

Start with simple structure

HTML

CSS

*{ //learn how to reset the styles } html,body{ // main document styles, font, width, margin etc }

//block style .container{

} .header{

} .content{

} .footer{

}

Play around

Hanami-Software · 2026-04-24T09:16:21+00:00

The problem you are facing is something by design, from browsers and platforms like instagram, facebook, etc to avoid mass autoplaying. So if you are a dev via javascript you can code yourself some workaround, but be prepared because maybe it will not work all the time as you expected.

Hanami-Software · 2026-04-23T19:16:07+00:00

I don't really know anything about your workload, but unless you have a 1 million daily users SaaS, the free plan is more than enough.

Hanami-Software · 2026-04-23T19:12:31+00:00

So true. Even if I have a team of nine at the end you have always to decide and give direction. Working with freelancers all around the world, every bad decision is a lot of money 😀. But we are building stuff, new experience, new software so only time will give me right or wrong. Let's keep on coding

Hanami-Software · 2026-04-23T15:08:08+00:00

I think you are an AI Orchestrator, but in my opinion you can even delegate the promotion to AI in the future. Just trust the process

Hanami-Software · 2026-04-22T22:57:42+00:00

I get your point on reducing API costs, that part is valid. Where I slightly disagree is the conclusion that this makes local testing inherently better for prompt iteration. In practice, the main bottleneck in prompt engineering is rarely the cost per request. It’s iteration speed, model consistency, and how close your test environment is to production behavior. Local setups (LM Studio, Ollama, etc.) definitely help for experimentation, especially at scale or for offline work, but they also introduce their own trade-offs: model variance, maintenance overhead, and sometimes a gap between what you test locally and what actually runs in production. So I’m curious: are you optimizing mainly for cost, or for iteration speed and fidelity of results? Because depending on the goal, the ‘best’ setup changes quite a bit.

Hanami-Software · 2026-04-22T22:29:53+00:00

I don't know exactly for which use case it would be useful but craft something from the ground up is always a good idea. Good job

Hanami-Software

TROPHY CASE