Meeting Minutes — 2026-01-15

Date: 2026-01-15
Time: 13:30–14:00 CET
Location: Google Meet

Attendees:

• Viktor Semenov
• Tom Grizetti
• Marco Potenza
• Edward Yusko
• Yurii Chabanov
• Mykola Surygin

Agenda

1. Document functionality still lacks global documents
2. Impersonation need to be NOT read only
3. Mobile application priority

Notes & Discussion

1. Document functionality still lacks global documents

HTMS wants to have global shared documents called Technical documents available for every authenticated MyMaxwell user. HTMS admins can edit them.

2. Impersonation need to be NOT read only

For the sake of support and flexibility we allow impersonation to be fully functional. This will allow to help resellers manage their installations, do orders, etc. And this is relatively easy to implement.

3. Mobile application priority

Viktor: Currently we have a native Android and iOS application that support read only view of MyMaxwell. And while it’s almost ready, deployment process is way more complicated than it is for web application. This may require supporting 2 concurrent API versions, forcing customers to update their app, waiting for Apple and Google application review, conform to their UI and UX standards (yes, they check this as well, especially apple). Even tiny visual change will require to pass through the whole flow. And at the very end MyMaxwell portal is a work application and we don’t expect users to chek their efficiency during commute.

Tom: We need this mobile functionality to enable technicians to do field work and customers to check their building status on the go. Also Inverstors like it.

Victor: Then we can do mobile web app. This means adjusting web interface for mobile device when open from the phone or tablet. This does not require installation, updates are simple and users never have stale version installed. Also it is easier to deploy and intergate with existing web functions.

Tom: Dev team should figure out how to make this technically. I’m ok with either option if it looks and behave like a phone optimized application: controls and text size should be adequate.

Decisions Made

• Native web application is not a requirement per se. Mobile view is a requirement.
• Impersonation should allow all actions of impersonated user, not read-only.

Action Items