Hi everyone,

I'm currently working on a native Tizen app (using C) and need to implement a background service that continues running even when the main UI is closed. I’ve gone through the official documentation, but I’m still confused about the best way to structure this — especially when it comes to inter-process communication and lifecycle management.

Specifically, I’d love help with:

How to correctly set up and register the background service in the manifest?
What’s the recommended method to send data between the UI and background service?
Are there any limitations on memory usage or execution time I should be aware of?

If anyone has experience doing this or has sample code to share, I’d really appreciate the guidance. Thanks in advance!

It would be beneficial to reference the provided materials, so I?ve shared the following guide links for your reference:

Background Category Setting:

https://docs.tizen.org/application/native/guides/applications/efl-ui-app/#allow_bg_table:~:text=Application%20Controls.-,Background%20Categories,-Since%20Tizen%202.4

The limits on memory usage and execution time are difficult to guide explicitly because system variables such as memory usage are applied in combination.

In the Tizen AppFW, various APIs are available for inter-app communication:

Data Control:

https://docs.tizen.org/application/native/guides/app-management/data-control/

App Control:

https://docs.tizen.org/application/native/guides/app-management/app-controls/

If you need to define complex protocols for inter-app communication, we recommend using TIDL as well:

https://docs.tizen.org/application/native/guides/app-management/tidl/

After checking the guide, use it according to the purpose.