Imagine: 200 ballots printed, 40 returned, voting drags on for a month, the chairperson manually counts votes. The result—low turnout, disputes over numbers, and piles of paper. We build mobile apps that turn this chaos into a predictable digital system. Over 30 projects for HOAs and management companies—a proven stack and ready-made modules allow launching an app in 12–18 weeks. Going digital saves up to 200,000 rubles per year on printing and mailing.
How do we ensure legal validity of voting?
Electronic voting must be legally clean. According to the Housing Code of the Russian Federation (Article 47), a meeting decision is valid if the owner's identity and awareness of the agenda are confirmed. During registration, the resident enters the personal account number, to which an SMS OTP is sent (0.5 rubles per ballot). After verification, the system assigns a "verified owner" status. The vote is recorded in PostgreSQL with a trigger that prohibits UPDATE after INSERT—achieving immutability. The protocol is automatically generated as a PDF with electronic signatures. Result: a meeting that used to take three weeks now takes 10 minutes, and turnout rises to 80%. Electronic voting is 15 times faster than paper.
| Field | Value |
|---|---|
| Meeting date | March 15 |
| Number of votes 'For' | 45 (75%) |
| Number of votes 'Against' | 10 (16.7%) |
| Abstentions | 5 (8.3%) |
| Transaction identifier | tx_9f4b2c1a |
Maintenance requests without a dispatcher
In a typical HOA, requests are taken personally by the chairperson. We ensure they receive instant notifications via push notifications (FCM) on iOS and Android. The HOA app is a single Flutter application with roles: resident, chairperson, employee. The user creates a request (e.g., "intercom not working") with a photo and geotag; the chairperson sees it on their phone and assigns a contractor. The status changes in real time—no need for the resident to call. This reduces incident response time by 60% compared to a paper log (from 8 hours to 15 minutes).
Why is financial transparency critical for HOAs?
Every owner has the right to know how their contributions are spent. By law (Article 161 of the Housing Code), the chairperson must report once a year, but residents can demand more frequent reports. The financial transparency module: the chairperson uploads a budget or report as PDF; residents receive a push notification and see the document in the app. No manual mailing. Fee payment via YooKassa or SBP with automatic receipt generation. Payment history by personal account is available at any time. Transparency reduces complaints by 40%—verified on our 30 projects.
| Task | Paper process | Digital app |
|---|---|---|
| Conducting voting | 3 weeks | 10 minutes |
| Processing a request | 8 hours | 15 minutes |
| Generating a report | 2 days | 1 minute |
How long does implementation take?
The full cycle—from analysis to store publication—takes 12–18 weeks. The cost is calculated individually based on the HOA's needs. We provide turnkey development: analyze requirements, design architecture, develop modules, integrate with 1C, test, and deploy. Warranty support: 3 months.
Typical implementation mistakes
We've seen dozens of cases where HOA apps failed. The main mistake is ignoring personal data security requirements (152-FZ). The second is poor integration with 1C, causing discrepancies in debt data. The third is lack of two-factor authentication, rendering voting legally void. We avoid these pitfalls: we use AES-256 encryption, certified engineers conduct code reviews, and each module undergoes audit for 152-FZ compliance.
Scope of work
- Requirements analysis and architecture design (2–3 weeks)
- Development of voting, requests, financial, and payment modules (8–12 weeks)
- Integration with 1C:Accounting if needed (1–2 weeks)
- Deployment to App Store and Google Play, push certificate setup (1–2 weeks)
- Training for chairperson and residents, documentation
- Warranty support: 3 months
Technology stack
Client: Flutter 3.x, Dart, GetX/Bloc. Server: Laravel 10, PostgreSQL 15, Redis, FCM. Document storage: S3-compatible cloud. Payments: YooKassa, SBP. Store builds: Fastlane with GitHub Actions. For iOS, we use automatic code signing with provisioning profiles and distribution certificates.
Implementation results
Based on 30 projects, switching to digital management reduces printing and mailing costs by 70%, and the time to collect meter readings by 12 times. Average meeting turnout increases from 30% to 85%. The accountant saves 4 hours per week on payment reconciliation. Contact us for a consultation on 1C integration and push notification setup. Request a demo of a working prototype—see all the features in action. Get a commercial proposal tailored to your modules.