Software consultancy
88 Analytics
We take over broken codebasesand ship them again
Hands-on engineering for stalled apps and messy backends. Flutter, Go, migrations, store releases. Flagship engagement: Dwellago, a buyer/seller real-estate matching platform we have been shipping for over a year.
3+ years · Canada, US, India
By the numbers
Small shop. Real delivery.
Years in Operation
Projects Delivered
Clients Served
Markets: Canada, US, India
Featured work
Dwellago
We took over a stalled real-estate matching platform and have been the hands-on engineering team on it for over a year. Flutter app, Go API, matching, and signed builds back into the stores.
Full case study- Client
- Flutter + Go buyer/seller matching app for real estate leads
- Scope
- Revival, Flutter migration, preferences/chat/photos/Stripe, matching, survey write fixes, AWS + Play/App Store redeploy
- Status
- Ongoing. Phase 4: ECS/backend ops and store builds after pre-migration apps were pulled
How we work
Same pattern as Dwellago. Stabilize, then ship.
01
Reproduce
Get a failure we can see. Logs, env, the exact path. No patch until we know what broke.
02
Stabilize
Make the repo build and the critical writes honest. Fix the corrupt rows and the 200s that aren't saves.
03
Ship
Features, migrations, matching, store builds against the APIs and schemas you already have.
04
Operate
AWS/ECS, signing, Play/App Store uploads, handoff notes. Keep it alive after the migration.
What we do
Same work we do on Dwellago, applied to your stack.
Codebase revival
Take over a stalled or abandoned repo. Get builds green, find the real failure modes, make the product operable before anyone talks about a rewrite.
Framework migration
Flutter tooling, Gradle/AGP, dependency recovery, Go API cleanup. Upgrade what you have so you can ship again. Not a vanity greenfield.
Write-path and debt fixes
The bugs that look fine in the client log. Survey saves that return 200 and do not stick. Corrupt rows. We fix the function the app already calls.
Store release engineering
Signed APK/AAB, package rename, upload keystores, Play Internal Testing, App Store redeploy after pulled builds.
Schema and API work
Ent/MySQL models, OpenAPI clients, custom REST when the generated client lags. Matching, preferences, location payloads that have to match production intent.
AWS / ECS ops
Backend deployment and day-to-day management for complex services. The unglamorous part that keeps a migrated stack alive.
What clients say
Short notes from people we shipped with
“They took a platform that wasn't shipping, got it runnable, migrated the Flutter app, fixed survey saves that looked like 200s but weren't, and kept communication clear while we worked through matching and store redeploys.”
“They built OCR for our archive and made years of paper searchable. Practical work. We spend less time digging for files.”
Engagement Models
Scoped to the work. Pricing tracks complexity and ownership. We quote what the engagement actually needs.
Technical Assessment
Codebase, architecture, and risk review with a prioritized remediation map
Scoped per engagement
- Architecture and debt audit
- Migration and risk map
- Effort and sequencing plan
- Written recommendations
Most requested
Project Execution
Defined revival, modernization, compliance, or schema engagements
Scoped per engagement
- Dedicated engineering ownership
- Framework and schema work
- Test coverage standards
- Milestone-based delivery
- Handoff documentation
Embedded Retainer
Ongoing technical capacity for platforms that need continuous execution
Scoped per engagement
- Reserved monthly capacity
- Priority response
- Debt and release support
- Flexible sprint scope
- Direct engineer access
Start with a technical assessment. Pricing is negotiated per engagement.
Got a stalled codebase?
Send the repo situation to sales@88analytics.com. We'll tell you what to fix first.
sales@88analytics.com