Hello,

Thanks for the PR.

I am not sure I quite understand what value would be brought to the user by adding such example. If the user already has an app using the callback model, it doesn’t seem difficult to add the right calls in the same place?

But conversely it becomes one extra app to maintain for us, if not four (because OpenGL, Vulkan, SDL GPU examples would in theory want the same treatment), and its an app that doesn’t follow the structure of others (so its harder to maintain), and imho, if I may say so, for an api which brings near zero added value and only adds restrictions to the user application.

Perhaps it would be a better use of maintenance energy to sprinkle 4-5 comments in our existing app to say, “hey, this block correspond to your SDL_AppIterate() block” etc. ?

Feel free to reject and/or close. I was new to SDL3 and imgui, so it took me a bit to grok this specific combination, so I just thought it'd be useful for someone that was new to both like I was. It only took 20 minutes to create so no loss if its tossed. I will keep it for my own future project skeleton purposes regardless.

You are pointing out a legitimate need, but I think it'll be too costly to maintain 4 additional examples along with the build files.
Instead what I've done is to add strategically placed comments in each the example:
a7657f2

I believe this gets us 90% of the way of facilitating integration for new users, while significantly reducing future maintenance.
Thanks for the suggestion!