Contact

Three things make a first reply useful:

• What the app does and who uses it. A field team, a warehouse, patients, your own staff. It changes the answer more than the screen count does.
• Which Xamarin version it is on, roughly, and whether it still builds. "We are not sure it builds" is a common and perfectly fine answer.
• What is forcing the change: a store rejection, an OS upgrade, a security review, an audit, or the person who understood the mobile code having left.

A senior engineer replies within one business day. First conversations are about what is in the app and what the options are; they are not a scoping exercise with a proposal attached.

If you would rather read first, what Xamarin end of support actually means is the briefing we would give you on the call, and the assessment page describes what a first engagement usually looks like.