Build Boomerang for Gmail
KINDAback to the verdict
Before step 1
you will need
- desktop development machine
- IMAP or Gmail OAuth credentials where supported
- secure local keychain access
Delivery order
Scaffold the smallest runnable application and document its commands.
done whenThe project starts from a documented command in a clean checkout.
Implement the primary data model and core workflow.
done whenThe main object can be created, read and changed end to end.
Add validation, safe failure states, and persistence.
done whenBad input is refused with a readable message and nothing is left corrupted.
Cover the critical path with automated tests.
done whenThe highest-risk behavior fails the suite when it breaks.
Exercise a clean install from the README and fix every missing step.
done whenA fresh clone reaches the first successful workflow using only the README.
That is the whole plan for Boomerang for Gmail. What it deliberately does not cover is below · check the gaps before you call it a replacement.
- team routing and shared inbox rules
- abuse response and security operations
- calendar-provider edge cases and timezone correctness
- provider-grade deliverability
- push reliability across devices
Need the files? The project pack on the verdict page hands your agent the whole brief · more email.