Adding tab strip service to //services

[Fred Shih]

Hello there,

We are currently building a tab strip API service that supports multiple platforms (e.g.: native desktop, webui, android, and maybe ios in the future).

We need to place the service in a shared component because we have several different types of clients. One example is webui and another might be extensions in the future. We were thinking of placing it under //components, but //components code should not depend on higher level browser concepts.

//services (and the servication effort) seem like a good fit, as it is meant to house general services that are tied to Chrome and the browser. However, this project seems inactive at the moment. Is it still possible to add new services here?

We also plan to add several services in the future, such as bookmark. If it is no longer possible to add components to //services, is there a better place to put these components? Thanks!

[Colin Blundell]

On Tue, Oct 7, 2025 at 12:58 AM Fred Shih <ff...@google.com> wrote:

Hello there,

We are currently building a tab strip API service that supports multiple platforms (e.g.: native desktop, webui, android, and maybe ios in the future).

We need to place the service in a shared component because we have several different types of clients. One example is webui and another might be extensions in the future. We were thinking of placing it under //components, but //components code should not depend on higher level browser concepts.

//services should "even less" depend on higher level browser concepts. What exactly do you mean by "depend on higher level browser concepts" here though? e.g. the iOS port can't share any code with //chrome.

 

//services (and the servication effort) seem like a good fit, as it is meant to house general services that are tied to Chrome and the browser. However, this project seems inactive at the moment. Is it still possible to add new services here?

We also plan to add several services in the future, such as bookmark. If it is no longer possible to add components to //services, is there a better place to put these components? Thanks!

Naively //components seems like the right place. Are you planning to run this code in a utility process or in the browser process? //services (and //components/services) are generally for code that needs to run in a utility process.