Textup — Second Phone Number
As many private numbers as you need, from one Flutter codebase.
- iOS
- Android
- macOS
- Windows
- Web
- Multiple per user
- Numbers
- 6 platforms
- Targets
- App Store + Play
- Stores
About
The Flutter rebuild of Second Line, now live on the App Store and Google Play. One codebase targets iOS, Android, macOS, Windows, Linux and the web. People pick US or Canadian numbers for calls and texts, and since version 1.0.7 they can buy several numbers on one account and switch between them in the app. I set up the layer split between domain, data and presentation, and wired in the APIs behind number purchasing, credits, call logs and messaging.
What shipped
- Multiple numbers per account: buy several and switch the active line in one tap
- One Flutter codebase built for six platforms
- Clean architecture with separate domain, data and presentation layers
- Number purchase, credit and billing API integration
- Calling, texting and voicemail at parity with the native app
- A shared design system across mobile, desktop and web
How it was built
Architecture
Domain, data and presentation layers defined up front so six targets could share one core.
Telephony parity
VoIP calling and messaging brought level with the native iOS product.
Commerce
Number purchase, credits and billing APIs wired through the data layer.
Form factors
A shared design system stretched to phone, desktop and web without forking the UI.
Multiple numbers
Several numbers on one account, with the active line switchable from anywhere in the app. Shipped in 1.0.7.
Challenges & solutions
ProblemSix platforms from one codebase usually means one good platform and five compromises.
SolutionStrict layer separation kept every platform-specific decision in the presentation layer, so the domain and data layers are genuinely shared rather than nominally shared.
Built with
- Flutter
- Dart
- Cross-Platform
- VoIP
- Multi-Number
- Clean Architecture