Post

The release also will introduce Foodnoms Cloud: a new account system and alternative sync service to iCloud. This has been in the works for over two(!) years now. I've put a lot of thought and intention into this new system.

Why I built Foodnoms Cloud: 1. Some folks can't (or prefer not to) use iCloud, e.g. due to low storage. 2. Relying solely on iCloud poses long-term risk for the product and business. 3. It unlocks new product opportunities for the future.

This is timely because I'm working on a new project and have been debating whether to use iCloud for sync or roll my own (which I have done before, so I am fairly comfortable with what's involved)... If you could go back would you still start with iCloud, or do your own thing from the beginning?

I lean toward still using iCloud at first, because it's one less thing to build. But I kind of dread a future where I decide I do want or need my own sync, and then having to either maintain two systems or migrate people…

Good question. I think it depends on the app. I wouldn't have been able to ship Foodnoms 1.0 without iCloud. But today, I could probably pull something together quickly with something like Supabase (which is what powers Foodnoms Cloud). And long-term that's less constraining and less risky.

0 reposts2 likes

No replies yet.