ShipNLaunch

Discover what people are shipping. Launch your product, explore new tools, and find makers.

[ShipNLaunch @ShipnLaunch]

https://t.co/YZTcKceRXa

[Zara Zhang @zarazhangrui]

Your personal website is the new resume

[ShipNLaunch @ShipnLaunch]

my twitter account

[Amondi @Amondi_y]

"the less people know about your process, the more space you have to actually grow."

[ShipNLaunch @ShipnLaunch]

@MusharofChy have you submitted ur product on @ShipnLaunch ?

[Sujay. @Sujay__Raj]

security has been a good reminder this week that the biggest problems aren't always in your application code.

a few things stood out to me:

eMudhra: Weak private keys in intermediate certificates raised serious concerns about HTTPS trust. Updating browsers alone may not be enough if your tools or containers use separate certificate stores.

PHP: Critical bugs can put a server at risk before your application code even gets a chance to protect itself. Keep the runtime patched.

Node.js: Runtime security updates matter too. Updating npm packages doesn't automatically update the Node.js version running in production.

The common lesson?

Your app can be perfectly fine, but the software underneath it might still be vulnerable.

If you're running production services, take a little time to:

-Check security advisories for your runtime
-Update certificate stores and rebuild outdated images where needed
-Rotate exposed credentials
-Review what is actually running in production, not just what your local machine has installed

One thing worth remembering: security isn't a one-time task you finish before launch.

It's part of maintaining a product.

And ignoring updates because everything seems to be working is a risk that isn't worth taking.

[ShipNLaunch @ShipnLaunch]

We’re shutting down too.

We don’t use php I just don’t wanna work tomorrow.

[MalShare @mal_share]

We are aware of the PHP vulnerability and are shutting down for the weekend.

[Olise @Olisehateshittt]

Become addicted to finishing things.
Not the idea. Not the plan. The finish.
Start small. Close the loop. Do it again tomorrow.

[Sujay. @Sujay__Raj]

It's appealing to build a feature because a competitor has it.

They have analytics, so you add analytics.
They have AI, so you add AI.
They have a dashboard, so you build one too.

But you don't know why their users need those features.

Maybe their customers asked for them.
Maybe they're solving a completely different problem.
Maybe the feature isn't even being used.

I'd rather talk to a few actual users before spending a week copying something.

A longer feature list doesn't automatically make a better product.

[Sujay. @Sujay__Raj]

People usually see the final product, not the random bugs, bad decisions, and hours spent figuring out why something isn't working.

that's most of my week building https://t.co/8TLzlRLfAT.

some days progress looks like a new feature. Other days, it's fixing one annoying issue.

both count, I guess.

[ShipNLaunch @ShipnLaunch]

@pelloiafilippo seriously canceling Claude next month?

[ShipNLaunch @ShipnLaunch]

ShipNLaunch was a pretty small idea when I started. now it has submissions, moderation, product pages, weekly discovery, voting search, categories, maker profiles and sponsorships. still plenty I want to change. but it finally feels like a product instead of a folder on my laptop

[Sujay. @Sujay__Raj]

ShipNLaunch DR is 24 now 🎉

0 ➡️ 24 in 18 days!

Moving up slowly (log curve). Still hopeful of hitting 40 in the next 2 weeks. #BuildInPublic

[Sujay. @Sujay__Raj]

15 product launches in a single week on https://t.co/8TLzlRKHLl 🤩

and we've now crossed 3k+ visitors! when I started building this, I wasn't sure how quickly things would move, so seeing this progress feels pretty special.

a few milestones along the way:

Sharing the journey and learning in public
Growing from 2k+ to 3k+ visitors
Seeing more makers bring their products to the platform

there's still things to fix, improve, and figure out. But it's encouraging to see people finding ShipNLaunch and using it to launch their work.

Now the focus is on getting more eyes on the platform through SEO, social media, and community building.

One step at a time. The next milestone is waiting.

[Hades @0xHvdes]

X is full of incredibly talented people, but most of them don't take content seriously

there are hundreds of ways to monetize your audience, and it only takes 1-3 hours a day to start building one

someone who's half as good as you but knows how to get attention will probably make 10x more money than you

something to think about.

[Sujay. @Sujay__Raj]

Your website is live. Here is what to check BEFORE spending a single dollar on SEO:

1. Open Google Search Console and verify your domain.
2. Submit your sitemap.
3. Check that important pages return a 200 status.
4. Make sure robots.txt isn’t blocking indexing.
5. Verify canonical URLs.
6. Give every core page a distinct title.
7. Add internal links to priority pages.
8. Test the site experience on mobile.
9. Audit and fix broken links.
10. Check PageSpeed Insights performance.

Don’t expect rankings overnight. The point is to fix basic technical blockers before paying for traffic or SEO campaigns.

Bonus: Most of these checks are completely free.

Save this for your next website launch.

[Sujay. @Sujay__Raj]

If your site works on desktop, that does not mean it works.

Test the actual flows on a phone:

Open the homepage.
Search for something.
Create an account.
Submit a form.
Read the pricing page.
Open a dropdown.
Tap every important button.
Try a long piece of text.
Look for the stuff developers miss on a big monitor:
tiny buttons
horizontal scrolling
menus that are hard to close
inputs covered by the keyboard
images pushing content around
slow pages on mobile data
I regularly find small issues this way on https://t.co/8TLzlRLfAT.

You don't need a perfect mobile redesign for every screen.

You do need the important actions to feel normal.
A user should not need to pinch, zoom and fight the UI just to finish one task.

[ShipNLaunch @ShipnLaunch]

Every developer eventually discovers that “quick change” is a dangerous phrase.

“I'll just change this one thing.”

3 hours later:

https://t.co/vrRYD6qK8L now has a completely different problem

[Sujay. @Sujay__Raj]

If your site works on desktop, that does not mean it works.

Test the actual flows on a phone:

Open the homepage.
Search for something.
Create an account.
Submit a form.
Read the pricing page.
Open a dropdown.
Tap every important button.
Try a long piece of text.
Look for the stuff developers miss on a big monitor:
tiny buttons
horizontal scrolling
menus that are hard to close
inputs covered by the keyboard
images pushing content around
slow pages on mobile data
I regularly find small issues this way on https://t.co/8TLzlRLfAT.

You don't need a perfect mobile redesign for every screen.

You do need the important actions to feel normal.
A user should not need to pinch, zoom and fight the UI just to finish one task.

[Cassandra Unchained @michaeljburry]

1. Never stop exercising or learning.
2.Accept compromise to begin relationships.
3. Manifest the power of compounding.
4. Never gamble.
5. Have kids and be a good parent
6. If it flies or floats, rent it.
7. Buy half the house you can afford.
8. Art in the eye of the beholder is cheap.
9. Be thankful for and to all.
10. Be charitable.

[Sujay. @Sujay__Raj]

there's a point in every project where the exciting features are mostly done and the boring work starts.
SEO.
UX.
Edge cases.
Empty states.
Performance.
that's basically where https://t.co/nlui67p5yl is getting more interesting for me.

[Sujay. @Sujay__Raj]

I'm starting to think the best launch directories aren't the ones with the most submissions.
They're the ones where the submissions actually help people discover something useful.

That's the standard I want https://t.co/nlui67p5yl to reach.