Thank you for your valuable opinion.

As an advanced user myself, remote control is important to me, but I also want to introduce more people to BitTorrent through a simple UI. Based on the comments, it seems I have missed the target for advanced users with these large cards, this is something I would like to improve.

What would you suggest? Should I offer two view modes, one with cards and one with a list? I could find a way to reduce the vertical height of the cards anyway.

In the near future, I plan to utilize the horizontal space to add filter and label management options, allowing users to quickly find specific torrents. I think displaying hundreds of torrents simultaneously isn't practical as I can't process them all. Instead, I believe a search bar and filters would greatly enhance the user experience. It seems people here would prefer a table view instead, like qbittorrent, what are your thoughts on this?

The search bar allows you to quickly search using the selected search engine. Google is just an example preconfigured in the settings, but you can configure any search engine of your choice. For example, you can add archive.org with the URL "https://archive.org/search?query=". While I may consider integrating a search feature with plugins in the future, I currently find the existing search bar to be a simple & time-saving shortcut for finding torrents online.

Regarding the package-lock.json, I understand your point. However, please keep in mind that PikaTorrent is a monorepo. It includes the website, app (web & mobile), desktop (electron), and CLI. There are numerous development dependencies that are not bundled into the final app.

> What would you suggest? Should I offer two view modes, one with cards and one with a list? I could find a way to reduce the vertical height of the cards anyway.

I'm personally not a fan of the card view in BitTorrent clients, but I'm not necessarily against having one, but it has to be more compact than what it is now. If you want to attract more advanced users, having a list view would be pretty important if you ask me. Having both could be an option.

But keep in mind that you don't have to satisfy everyone, because that's not even possible.

> In the near future, I plan to utilize the horizontal space to add filter and label management options, allowing users to quickly find specific torrents. I think displaying hundreds of torrents simultaneously isn't practical as I can't process them all. Instead, I believe a search bar and filters would greatly enhance the user experience. It seems people here would prefer a table view instead, like qbittorrent, what are your thoughts on this?

I personally use Transmission and the default view is compact enough for me. Search for the torrents loaded into the client is a must for me, but I personally don't really care about labels. But that's just me.

> Regarding the package-lock.json, I understand your point. However, please keep in mind that PikaTorrent is a monorepo. It includes the website, app (web & mobile), desktop (electron), and CLI. There are numerous development dependencies that are not bundled into the final app.

That's fair I guess… but homepage alone seems to have 1202 dependencies (180 of them need funding and one is deprecated), seems a lot for 2 static pages. I'm not the one that will have to maintain it, but at some point something will break… Also the performance of the homepage seems to impacted by the frameworks used[1].

1: https://pagespeed.web.dev/analysis/https-www-pikatorrent-com...