What's Good About the Arc Browser
chriscoyier.net
chriscoyier.net
Some things that seems to me to be good ideas, mentioned there, includes: split-screen, tab renaming, boosts (hopefully, they will be documented), DevTools.
But, needing an accout seems a bad idea. A web browser should just as well be usable to display local HTML files even if you do not have an internet connection, too; and, to make it good should also need FOSS.
I think many problem that Chrome does, although, they say that the dev tools is good. Well, making a new web browser will need also the web dev tools, in order to be good.
Actually, I think that one thing to make a better one, will be that many things of extensions (e.g. user CSS, header overriding, etc) will be core features, and file formats and protocols will be extensions (some of which, such as HTTP(S), PNG, etc) will be included by default. (A few things will be built-in, such as the data: scheme, and the HTTP request/response model (but not implementation).)
(Being able to write extensions in native code also would be very helpful, but most don't do that, or do it badly.)
It has some nice UI/UX features. For power users of Firefox or Chrome, many of the features can be replicated by various plugins, etc. What's nice about Arc is that it's all integrated and built-in.
For example, I had different user profiles in Firefox (work, personal, etc.) so the cookies and search history were separate and also tabs on the side instead of the top.
Lots of these features appear in different browsers; but arguably, Arc is one of the first to include all of them be default in an accessible UI. I think Vivaldi has many of the same features but it has so many features that it can be a little overwhelming. Arc's features are a lot more accessible.