This is a cool product, but it feels a bit confused.
It seems the innovation here is making the management, editing and publishing of emails much more streamlined through your interface. That's great as it's definitely a frustration of creating emails.
But in the pricing you are focusing on contacts (and therefore "number of emails sent"). First of all, it's very difficult to guess what "contacts" are when considering transactional emails. What if a new user signs up but never uses the app again? Is that a new contact? If I send one marketing email it could be to 200k contacts, but I may only have 1000 transactional emails/contacts per month.
Instead of focusing the pricing around contacts and "emails sent" why not allow customers to "bring their own email platform". This would absolve you of having to worry about email pricing. A custom can connect SendGrid, MailGun or whatever they want. You can then focus your product on the publishing experience (and probably charge a lot more)
Thanks for the detailed feedback! We find that users start their company, use us for everything then never have to think about how to contact their users. Requiring a bring your own solution is great for more mature businesses but we’re targeting early stage right now and asking someone to signup for a second service to use ours feels like it may slow things down.
I've updated my blog post to include 1Password in the title as it contributed to the issue (I can't update the title here). That said, I've never experienced this before, having used 1Password on 100s of other payment forms so something is up.
I do think there are design issues with people being able to set subscription amounts manually without having a confirmation step when doing so.
1password payment form filling works fine so rarely for me, I usually copy just number by hand. I wonder if that's somehow specific to Russia (field names are still in english, but it doesn't seem to help much)
Interesting point, I hadn't actually considered what the power consumption of RPis is. I use a few around the house to do various things. Honestly though, the only reason I've used one here is that it was lying around unused. As you mentioned, if I were buying something myself I'd use a different, smaller controller.
I mentioned this in a HN post in the past regarding standing desks, mentioning that I'd created an over-engineered standing desk controller (using a Raspberry Pi) over lockdown as as little fun project. Somebody asked about a write-up for it, so here it is
You say it's over-engineered, but every time I read it I think of something Mr. AvE said about the topic (albeit with physical materials, regarding Juicero, to be precise):
If it uses more material than required for the job it's over-built and under-engineered. Your solution seems to be massively that.
If you have some disposable income buy an Arduino kit from say elegoo. They come with a lot of little labs, basically 30 min - 1 hour exercises where you take one of the 30 physical devices it comes with and use it.a little bit of Lego like assembling of parts and copying some code from GitHub.
So like a led (light) is one lab. The next might be a photo sensor (signal with amount of light). After these two labs you can now make a night light. Or a rave strobe.
Do the switch or button lab and you can turn it on or off or change the pattern. After 30 labs you have a pretty good idea of what to do.
Now buy an esp32 that works with a breadboard and if you know basic http you now have an iot device.
I recently hooked an esp32 to a dht22 and started graphing temp in my gourmet mushroom enclosure in about an hour of watching baseball. Just sends data to influx and grafana on an rpi data hub
A portfolio page is very different to a resume page. Your portfolio is your professional landing page. It might include a blog, relevant profile links, recent projects etc.. A resume _could_ be a part of this, but it's only one part of many. A portfolio is generally intended to drive traffic. For example, if you begin blogging about a particular technology, you can expect to start getting traffic from people searching that technology. This might lead to recruitement and inquiries. You will generally want to it show first on Google when someone searches your name.
If you just want a single-page resume, you don't need to do anything as fancy. Create an index.html and get a nice clean stylesheet to format it. Host it for free on S3 and off you go. I wouldn't overthink the "features". Who is going to CURL your resume?
For reference, I have a pretty active portfolio site that receives a lot of traffic via the blog from Google:
Thank you for your comments. I'm a bit undecided as to what the purpose of the site I'm planning is. Part resume, yes, but also sort of a business card, with links to my things in a central place.
Yours is a very appealing site. Thank you for sharing.
This is a little project I started up to map all the pubs here in Dublin, Ireland that have a fireplace. It got some good feedback via Twitter (@pubswithafire) and I've since had over 500 pubs added all around the world.
I'd love to get some more good pubs added as well as some feedback and ideas of where to take it.
This is a little project I started up to map all the pubs here in Dublin, Ireland that have a fireplace. It got some good feedback via Twitter (@pubswithafire) and I've since had over 500 pubs added all around the world.
I'd love to get some more good pubs added as well as some feedback and ideas of where to take it.
This is a little project I started up to map all the pubs here in Dublin, Ireland that have a fireplace. It got some good feedback via Twitter (@pubswithafire) and I've since had over 500 pubs added all around the world.
I'd love to get some more good pubs added as well as some feedback and ideas of where to take it.
It seems the innovation here is making the management, editing and publishing of emails much more streamlined through your interface. That's great as it's definitely a frustration of creating emails.
But in the pricing you are focusing on contacts (and therefore "number of emails sent"). First of all, it's very difficult to guess what "contacts" are when considering transactional emails. What if a new user signs up but never uses the app again? Is that a new contact? If I send one marketing email it could be to 200k contacts, but I may only have 1000 transactional emails/contacts per month.
Instead of focusing the pricing around contacts and "emails sent" why not allow customers to "bring their own email platform". This would absolve you of having to worry about email pricing. A custom can connect SendGrid, MailGun or whatever they want. You can then focus your product on the publishing experience (and probably charge a lot more)