4 ms·

Came up with the idea for this with my wife and decided to build it! Been dogfooding it with my family and am now sharing it with the rest of the world. Tech s

Came up with the idea for this with my wife and decided to build it! Been dogfooding it with my family and am now sharing it with the rest of the world. Tech stack is Node/Express running on Dokku/Digital Ocean for the API. UI is built using Parcel and hosted on Netlify. Would love to hear your thoughts and happy to answer any questions you folks may have :-)

sokoloff 8y ago
I run a similar for my family and deliverability has been the on-going issue. Every year or so I have to make some kind of update because some mail admin or other changes their setup and they start flagging our outbound mail (from foo@sokoloff.com) as junk/spam. It's a good idea and I wish you the best of luck, but I am curious how you handle the outbound deliverability.
- jesperht 8y ago
  Thanks for the feedback! This is certainly a concern and one that I've tried to avoid by focusing on receiving (forwarded) email and not sending for the following reasons: * Easier setup - nothing to configure and you can keep using your existing email setup. Using email clients can be very difficult for some people, especially older folks, so I don't want to make their lives harder by forcing them to learn something new. * Less maintenance/upkeep - not having to worry about storing/sending/retrying means that users have a better UX. I'd love to easily integrate sending from the custom email, and I may add it in the future for the power users, but I think the cost/benefit of it right now just isn't worth it so I'll keep things Simple©.
indigodaddy 8y ago
Assuming you are making use of Netlify's Identity service, and also their free tier value added dynamic integration leveraging Lambda?
- jesperht 8y ago
  Netlify is purely hosting static content and proxying requests to the API on DO which is doing all the dynamic stuff.

4 ms·

Came up with the idea for this with my wife and decided to build it! Been dogfooding it with my family and am now sharing it with the rest of the world. Tech s

by jesperht 8y ago

sokoloff 8y ago
I run a similar for my family and deliverability has been the on-going issue. Every year or so I have to make some kind of update because some mail admin or other changes their setup and they start flagging our outbound mail (from foo@sokoloff.com) as junk/spam. It's a good idea and I wish you the best of luck, but I am curious how you handle the outbound deliverability.
- jesperht 8y ago
  Thanks for the feedback! This is certainly a concern and one that I've tried to avoid by focusing on receiving (forwarded) email and not sending for the following reasons: * Easier setup - nothing to configure and you can keep using your existing email setup. Using email clients can be very difficult for some people, especially older folks, so I don't want to make their lives harder by forcing them to learn something new. * Less maintenance/upkeep - not having to worry about storing/sending/retrying means that users have a better UX. I'd love to easily integrate sending from the custom email, and I may add it in the future for the power users, but I think the cost/benefit of it right now just isn't worth it so I'll keep things Simple©.
indigodaddy 8y ago
Assuming you are making use of Netlify's Identity service, and also their free tier value added dynamic integration leveraging Lambda?
- jesperht 8y ago
  Netlify is purely hosting static content and proxying requests to the API on DO which is doing all the dynamic stuff.