Or by posting it in our MVP chat channel - when there’s some finer points to work out, this can be incredibly helpful as all of us MVPs are long-time users, and there are a few members of the Xojo staff constantly monitoring this as well.

By forwarding the concern on to Geoff Perlman, Dana Brown, or Alyssa Foley - when it’s major, having direct access is great.

By messaging an engineer to clarify how something is supposed to function - knowing which team member(s) generally work on which part(s) of Xojo, I can usually get a quick answer when there’s a question like this by sending them a direct real-time message.

By opening a Feedback Case - if it’s a bug or feature request, this is usually the best way forward.

There are a few different ways I handle that information:

I then distill that down, hopefully into a paragraph or two, and discuss it with the Xojo team. I spend time with these users and try to determine what they need that they aren’t getting, or how Xojo might take steps to ease whatever suffering the user is experiencing. Personally, I hear from a fair few members of the community about concerns they have. Sometimes that’s a lot of work, sometimes not. We try to facilitate communication between Xojo the company and Xojo the community, and we advise Xojo on new features that will be coming to the language. Xojo’s MVP page spells it out pretty well. So, what’s expected of us and what do we really do? What We Do Some say it’s just a shiny pin on our lapels, others expect us to be Xojo’s de facto QA. There seem to be a lot of misconceptions about what the MVPs do.

Xojo web controls