A common observed use case is a users desire to create either: - a headless system which loads their application (likely a daemon, perhaps not) at launch or - a graphical environment which boots into a single application, a kiosk-mode It'd be great to support these work flows in the hob. Perhaps a wizard can guide the user through these common usage models? Here's a high-level possible work flow for such a wizard. "Build a custom Linux to run my app" "Which recipe provides the app you want to run?" << User presented with a filterable list of available recipes >> << Wizard tries to work out if this is a headless or graphical app>> "Build a kiosk-mode image for [APP_NAME]?" OR "Build a headless image for [APP_NAME]?" << User is presented with a list of executables and scripts generated by the recipe to pick which is the focus app>> "Great, let's build a [KIOSK|HEADLESS] mode app for [APP_NAME]" << User is presented with an overview of how the image will be constructed. Its contents, the focus app and how that will be started>>
Hi Belen, This bug seems fall into the category of potential feature requst for web-hob so assign to you to be included in your web-hob bin list.
We're looking at things like this as part of the overall developer experience work. This doesn't easily translate into any of the work items there but it will not be part of HOB so closing as won't fix.