![]() Any draft PRs are welcome as well, feel free to assign to me and I’ll add anyone else necessary for review from our end. Please let us know if you have any other questions.Īlso looping in as he’s much more familiar with the mobile platform than I am and can offer any other color or help/assist answering any questions you may have as you explore your technical approach. I would recommend taking a look at how you would approach doing this within Xamarin, or working around Xamarin w/o breaking stuff (obviously ), but ultimately would need the settings from the app’s primary screen (dotnetcore + Xamarin) to feed into the behavior. ![]() Per your thought that on background the connection would be closed and on open re-engaged, I believe the areas of concern for hooking into that are in the primary file. All service injection has abstractions setup either in Core or App, this I believe would go in App (but not married to that). ![]() Quite not sure how this would work to be honest but that would need to be figured out. I imagine this would also be structured as a service that would be injected into the necessary handlers to be invoked which wrap the native implementation(s) of the necessary APIs/frameworks. The likely starting place in mobile would be within the UI/UX approach, our preference would likely be a setting on the EnvironmentPage and work backwards from there regarding the settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |