Working with services that are competitors of each other is pretty good
Rules!
Working with services that are competitors of each other is pretty good

Rules!
- Each service are better to use with an opposite company (sub/root) service
- Not to use many solution of the same company for many similar tasks
- (All data must lands in one place or many other places?)
- Services working together, also if you do not want to…
- You can probably avoid unnecessary data duplicate this way
Examples:
- Not to use Analytics (bravely use other FOSS alternatives, like Umami and friends)
- Not to use Gboard (bravely use Swiftkey or other professional Android keyboard)
- Not to use 3rd party cookies (default on Brave browser)
- Not to use X (bravely use Mastodon)
- Not to use Google Translate (bravely use DeepL)
Should prevent, what can be prevented.
메타데이터
- post_id
- a36984470b6b
- slug
- working-with-services-that-are-competitors-of-each-other-is-pretty-good-a36984470b6b
- url
- https://medium.com/@iamdtms/working-with-services-that-are-competitors-of-each-other-is-pretty-good-a36984470b6b
- canonical_url
- https://medium.com/@iamdtms/working-with-services-that-are-competitors-of-each-other-is-pretty-good-a36984470b6b
- author_url
- https://medium.com/@iamdtms
- status
- ok
- fetched_at
- 2026-07-12 01:44:19