
DID
Add superior authentication to your website
Back in March we heard from Y Combinator that our application was successful, our interview was sound and that we were accepted into YC's Summer 2020 batch.
Demo day is 5 days away and we can now (at last) announce YC's investment in the open. We are now focussed on our new product Plum Mail.
Plum Mail makes use of our passwordless authentication technology and actually it's central to Plum Mail's vision.
Please check out Plum Mail and hop on the waitlist which, I am delighted to say, is growing nicely!
YC has been an incredible journey. This was the first fully remote batch at YC and the partners have been fab to work with. We have both learned so much and met some brilliant people.
We are more than happy to chat about applications and interviews with anyone applying to YC's next batch. Ask us anything, if we can answer it, we will.
Richard and Peter

##Do you onboard users?
Eliminate the friction from your onboarding with DID.app's magic invite links.
If you have a waitlist, onboard teams or your users collaborate in their accounts we can help.
We have a limited number of trials ready to use DID.app's new magic invite links.
Check out the magic invite links docs here and email me personally if you'd like to get started: richard@did.app
##Magic Invite Link Use Cases
###Waitlists
One click sign up via email. What better way to supercharge your conversion rate from waitlist to user?
Magic invite links are single use and both 'sign up' and 'sign in' the user.
###Team Members
Your colleague signs up to example,com and wants all their co-workers to jump onboard.
Well now they can in just one click.
Use DID.app's API to automate magic invite links.
We're working with an b2b ecommerce app in Brazil to onboard team members.
###Collaboration & review
User A wants to share their work with User B but User B isn't registered in your application yet.
With a magic invite link, User B is not only signed up with one click but is automatically sent to the page of content being shared.
We're working with a VC engagement platform in California to improve collaboration and review with magic invite links.
###Family and Friends
Magic invite links are a great way to onboard family and friends to your application for easy sharing.
We're working with an electric car charging service in India to implement easy family sharing.

Comment
https://did.app/docs/single-page-app-integration/
We added support for PKCE and other niceties to make using DID .app in a Single Page App (SPA) that much easier.
This should make it that much easier to add passwordless authentication to your rich client apps.

Comment
They say you should always listen to and engage with your users and I couldn't agree with the sentiment more. We launched a public roadmap (https://did.nolt.io/) a while back and the response has been fantastic.
The roadmap has ten features on now that are all genuinely requested by our users and today we are very pleased to announce that we've taken a very popular feature request (with 7 upvotes) all the way from idea through scoping to shipment.
I think this is a really important milestone to mark. Shipping features happens all the time (lord knows we got a whole lotta ideas for new features!) but listening to and acting on feedback from your users seems much more valuable and significant.
The feature we shipped is the ability to customise authentication pages for your apps: https://did.app/docs/customise-authentication-pages/
If you haven't already set up a roadmap, do. Initially I was worried about revealing our feature ideas (perhaps to the competition) or revealing that we have lots of feature ideas that just weren't ready yet but honestly, chatting to our users they are cool with the fact we're still building things, cool with the fact we're up front about our plans and very cool with the fact they can contribute to the features we develop.
Thank you to everyone who requested and upvoted the custom authentication pages feature.

Comment
https://www.producthunt.com/posts/did-app
Today we launch on product hunt.
We have done some homework, tried to polish our message, to make the website look nice and to make the relevant information easy to come buy. Much of the most useful feedback has come from the great indie hackers community.
What we haven't done is line up hunters or anything more involved in that. In all honesty it's because we'd rather be building things and talking to customers.
Let's see if we've done enough. We would love your support and of course give you a break down of how it worked out once we know

5 Comments
5 Comments
-
2
Gave you an upvote - as a front end dev I definitely prefer Auth to be handled by an external trusted service - I guess that’s a difficulty for you, how to build trust that it’s secure - I just use Google Auth at the mo but I like that yours gives the user privacy. Good luck with it 👍
-
2
Thanks so much Jamie :-) I'm excited about open sourcing elements of DID and hopefully that transparency and invitation to collaborate will engender trust in a meaningful way.
-
2
We plan to open source the client, which would allow people to independently verify that we use the keys correctly and that they are stored securely in the browser.
-
1
Nice one, sounds good
-
-
-
1
Exciting day @crowdhailer, the culmination of a lot of hard work over the last few months.
-
1
Upvoted!
did.app
Over the last few months we have been working hard to enable anyone building a website or app to be able to get awesome passwordless authentication done in just a few minutes.
We recently finished all the code for account creation and management. Now anyone can visit did.app and get setup in minutes.
Up to this point we have had to manually onboard users which was slow but taught us a lot in the process.
In the coming weeks we will be looking at other places to spread the word, but for today we would love a retweet.
Thanks, and I hope everyone has a lovely day.

Comment
We relaunched our web app for passwordless authentication this week. The design is trying to be a bit more fun but still serious enough for a project that you need to trust for security.
We are looking for your feedback, check out our preview page allows you so see all the pages in the webapp.
mydid.dev/preview#EnrollCredentials
It is build with svelte.js and tailwind CSS. Both of which I can highly recommend. We would be interested in hearing other people experience with either technology.

Comment
We added 10 new people to our mailing list for updates to did.app.
The most we have added in one week.
Keeping this list increasing is really useful for us as we hope to be announcing our new release soon.
The majority of our traffic came from twitter this week. Much of that because we engaged with a thread started by Troy Hunt. A big deal when it comes to talking about passwords.

4 Comments
4 Comments
-
1
That’s great! How are you managing your mailing list? I need to get one going myself.
-
1
We just keep them in mailerlite.com I believe.
-
Finding a suitable name (and domain) for your project is a huge challenge and one we thought we had solved until we asked this question of the amazing Indie Hacker's community:
https://www.indiehackers.com/post/how-bad-is-our-startups-name-a7d69c0e60
Turns out, our original name (Kno / trykno.com) is pretty terrible mainly from a pronounciation point of view.
So, after some soul searching and, of course, asking IH what you thought first (https://www.indiehackers.com/post/how-is-our-new-name-did-76f2c2f017) we came up with a new name:
DID
Today we are working on re-branding our project across all its touchpoints. Hard work but hopefully it will be worthwhile in the longterm.

Comment
trykno.com launched in July 2019 so in 14 days, we've generated the same amount of traffic to our website as we managed to generate in 7 months.
Here's a challenge, have you passed the same milestone? If so, how quickly? If not, when do you expect to pass it?
Wouldn't it be great if we managed to do this every January! That would certainly represent a steep growth curve.
#gopasswordless

3 Comments
3 Comments
-
2
In answer to both comments from @gregjw and @nh2_amine, we have started to create content in the form of articles that we published on our website and we then went to watering holes for our audience and found ways to share the articles. This generated quite a lot of traffic. The other big source for us was writing different integrations for our product and publishing repos on Github. This then gave us the ability to reach out to language-specific communities such as Rubyflow. This generated lots of traffic very quickly.
-
1
What'd you change in your approach for such a shift?
-
1
That's graet news! What did you do to grow your traffic this much in just 14 days?
About
The current reality of authentication online personally irritates me, particularly now I am convinced that better options are not just possible, but viable and in demand.







35 Comments
What do you think from your experience the product should be like to be accepted? I mean does it have to be something completely new or just a well-made product overall? Maybe some product categories are more preferable than the others?
You need to demonstrate that people want it. YC's mantra is 'Make Something People Want'. Whether it's a new idea or you're simply replicating someone elses idea (but doing it 10x better) the best way to get your product into great shape is to find people that want it and shape features around them.
So, a very basic product concept with genuine user interviews where users say - yes, this solves the problem I've got, when can I have access to the product?' is a stronger hand than a product which is very well built, has lots of features and you've spent months developing it but has no user insights.
Does that make sense?
As a secondary point, reading between the lines, your question assumes it is only the product that is important when the partners consider your application. You and your co-founding team are also a large part of the application's success.
That's a very interesting insight, thanks!
You're very welcome :-)
Congratulations on the launch! I've always had the problem of organizing my email thread recipients, so I'm excited to see where this goes.
Did you hop on the waitlist? I think this is the easiest way to stay in touch.
I haven't signed up yet, will check it out!
Thanks so much! Me too.
Hi y'all. We are launching Plum Mail on Product Hunt today.
If you like what we're doing please check it out! We'd love an upvote.
Thanks so much for your support. Don't hesitate to ask me for the return favour.
Congratulations! I’m building my product using YC SUS. Hoping to get a lot of value before applying. My question is, what’s your approach to getting customers to wait for your release? What’s the process for signing them up?
We also graduated from SUS, at the time I struggled to engage with it (some of the video calls we had were quite poor quality) but having been through YC's process there are so many similarities with SUS. I totally get it now.
SUS is a very good way to prepare for YC and I think graduating from SUS before you apply is a good move. Mention that in your application. Take the video calls, engage with them, don't be afraid to politely encourage others on the call to move the conversation on if it's stuck on a particular point. Some people to like to talk and dominate sometimes! haha.
The approach for getting anyone to sign up to anything is to build something they want. That probably sounds too simplistic but it isn't.
We currently have an email address which is: yesplease@plummail.co and we're asking people that like what we're building to email that to get a place on the waitlist.
It's working well. When people email they are writing a little something about why they would like Plum Mail and this is enormously insightful.
What's your product? Is it here on IH?
Thanks for the advice, I'll make sure to take the program as serious as possible and get the most out of it. It's great to see that you all took that same approach and got great results.
Our product is on here.
We're an online driving platform working with delivery companies & independent drivers across the country to meet a rapidly growing need to hire/contract reliable drivers.
https://www.thedrivingbureau.com
I have some perspective clients, but we haven't collected credit card information but they are ready to jump on board.
To be direct, if you can convert those customers, get the revenue and get their positive engagement with your product then that traction will be a great strength in any YC application or interview.
Nice work guys! I look forward to seeing the roadmap.
Thanks so much! Yea me too. I have so many feature ideas that you can build in Plum Mail that you just can't offer in a traditional email client. They need an upvote system really. We used Nolt before, might use it again unless you happen to know of a good alternative?
I'm applying to YC and I realize that at least one of the founders should be a technical founder. As of now, I'm the only person working on my idea and I have only very basic programming experience—past the MVP, I will need to find a co-founder to work with for the programming aspect of the product.
However, I'm hesitant to do that right away because (due to the very unusual circumstances of today) I wouldn't be able to spend a lot of time in person with this co-founder. I feel like jumping into a co-founding relationship right now would cause issues with trust, productivity, synchronization, etc.
My question to you is whether it's a better idea for me to ramp up my programming self-teaching starting now, or whether I should adapt to the circumstances and find a technical co-founder now? Thanks and congratulations on Plum Mail, it looks super cool!
This is tricky! YC aren't going to check your coding 'certificates' as such but the reason I think they are keen for you to have a technical founder on the team is so that you can move quickly, build things, iterate and make impressive progress.
If you entered into YC with the view that you needed to hire a programmer then that will take weeks and slow you down so so much.
However, there are solo founders that I know need extra coding help. Usually they're great at one aspect but not the other, maybe they're great at backend but not front end.
Also, on the co-founder front, you're intuition is spot on is my feeling. I am so fortunate that my co-founder and I have known each other for 15 or so years. We are good friends, he knows my flaws. Building a startup is high energy. There are highs and lows that will test your relationship. You need to have a strong relationship with your co-founder for all the reasons you say there.
Honestly you should probably do both of those things. You only stand to gain by learning more coding and it's so easy to access online learning these days at places like codeacademy. And, even if you become the technical co-founder with your newfound knowledge of programming you'll probably want a non-technical co-founder!
There are lots of jobs in your startup that definitely don't need programming skills like sales, marketing, relationship building, having meetings with potential investors, sorting out all kinds of weird legal company stuff oh and working the Indie Hackers forum of course ;-)
Does this help?
If you would like to sign up to our waitlist for Plum Mail, please do. Email:
yesplease@plummail.co
Congrats! What's been the biggest source/driver of waitlist signups (IOW, where are they coming from)?
Thanks. Trying really hard to get to the kernel of value that Plum Mail offers as quickly as possible and sharing that with people you think will care. A lot of targetted manual sharing.
Indie Hackers is a great source of conversation, we're launching on Product Hunt tomorrow, you've got Hacker News, SUS, Betapage, Betalist and a load more.
Oh, one more question, if you have time:
How did you decide to have people send you an email rather than providing a form for getting on the waitlist?
This is a bit counter-intuitive. We can very easily (like 3 minute's work) add a sign up box and we nearly did yesterday but when people sign up for the waitlist using yesplease@plummail.co you know they've put in that extra effort to join the waitlist because it's a manual step for them.
Also, people are writing interesting things about why they would want to use Plum Mail.
I say this is counter intuitive because we've deliberately added a little friction into our sign up flow for the waitlist. But this I think helps ensure the users that are signing up are really genuinely interested and it's not a throwaway gesture.
As we continue to validate Plum Mail, there is no point optimising for a vanity metric. We need to optimise for honest, meaningful feedback.
So, the fact people are making the effort to email us and sign up the waitlist is now a very positive signal.
That's how I've interpreted what's going on anyway, do you have any thoughts? Have I misjudged this at all?
This may be of interest. I've met some really cool female founders this summer: https://blog.ycombinator.com/category/female-founders/
Thank you!
I was wondering if this ^ was the reason :-) It hadn't occurred to me to do it this way until I saw your landing page. But it sounds like it's worked well for you. So thanks for the answer because it adds another tool to the toolkit in the future!
You're welcome. As you know we popped Plum Mail on Product Hunt for their last cycle and the waiting list has gone bonkers with sign ups! Some have not written anything about why they want to use Plum Mail but the majority have and it's so (so) useful to see the comments. Sometimes people say which feature they are looking forward to using and others resonate with the problem we're solving. Being honest with you, this is the first time we've taken this approach. With DID.app, we used a form and yes we had loads of sign ups but zero insight.
If we sacrified a percentage of conversion by not having a form input then I'm totally happy with the upside which is the insight.
Might not work for every idea or everyone but anecdotally it's been an interesting experiment and these were the results for us.
Thanks. It's actually quite informative to see this list, even if it might seem like the 'usual suspects,' heh. I'm always curious to see if other folks have any kind of direct pipeline into a channel of targeted customers. It's good to see that early traction happens lots of different ways :-)
oh man totally forgot Reddit, Quora, Hashnode, Dev.to etc. If you're building something that resonates with a niche then there will be more targetted channels available to you. However, these will take more work to get into.
Thanks for this! Yeah, my own list is quite big. And it sounds like, from your experience, it's not a bad plan to go after them all.
Hi Richard. Congrats on getting into YC and all the best for demo day! I am planning to apply to the next batch. How can I reach out to you? I'd like to get some advice and just hear what your experiences have been like.
Hey Makulis, we can have a video call tomorrow if you like. Say 15 minutes.
One thing I've learned during this remote batch is you gotta get good at video calling!
Or; please email me (richard@plummail.co) - we can set up a call there.
And also don't forget to sign up to our Plum Mail waitlist by emailing yesplease@plummail.co
Thanks!
Richard
I sent you an email from lincoln.nxumalo@gmail.com
Thanks. A video call will be great! I'll drop you an email and you can suggest a time. I'm pretty much available the whole day tomorrow. I'm in South Africa, so we'll just need to take the time zones into consideration.
I'll definitely sign up. I like what you are building.
Cheers! Looking forward to connecting with you later today.
@richardesigns congrats on getting into YC and getting through it. I look forward to seeing what you accomplish.
Thank you, :-)
This comment was deleted 6 years ago