Craft and publish engaging content in an app built for creators.
NEW
Publish anywhere
Post on LinkedIn & Mastodon too. More platforms coming soon.
Make it punchier 👊
Typefully
@typefully
We're launching a Command Bar today with great commands and features.
AI ideas and rewrites
Get suggestions, tweet ideas, and rewrites powered by AI.
Turn your tweets & threads into a social blog
Give your content new life with our beautiful, sharable pages. Make it go viral on other platforms too.
+14
Followers
Powerful analytics to grow faster
Easily track your engagement analytics to improve your content and grow faster.
Build in public
Share a recent learning with your followers.
Create engagement
Pose a thought-provoking question.
Never run out of ideas
Get prompts and ideas whenever you write - with examples of popular tweets.
@aaditsh
I think this thread hook could be improved.
@frankdilo
On it 🔥
Share drafts & leave comments
Write with your teammates and get feedback with comments.
NEW
Easlo
@heyeaslo
Reply with "Notion" to get early access to my new template.
Jaga
@kandros5591
Notion 🙏
DM Sent
Create giveaways with Auto-DMs
Send DMs automatically based on engagement with your tweets.
And much more:
Auto-Split Text in Posts
Thread Finisher
Tweet Numbering
Pin Drafts
Connect Multiple Accounts
Automatic Backups
Dark Mode
Keyboard Shortcuts
Creators love Typefully
150,000+ creators and teams chose Typefully to curate their Twitter presence.
Marc Köhlbrugge@marckohlbrugge
Tweeting more with @typefully these days.
🙈 Distraction-free
✍️ Write-only Twitter
🧵 Effortless threads
📈 Actionable metrics
I recommend giving it a shot.
Jurre Houtkamp@jurrehoutkamp
Typefully is fantastic and way too cheap for what you get.
We’ve tried many alternatives at @framer but nothing beats it. If you’re still tweeting from Twitter you’re wasting time.
DHH@dhh
This is my new go-to writing environment for Twitter threads.
They've built something wonderfully simple and distraction free with Typefully 😍
Santiago@svpino
For 24 months, I tried almost a dozen Twitter scheduling tools.
Then I found @typefully, and I've been using it for seven months straight.
When it comes down to the experience of scheduling and long-form content writing, Typefully is in a league of its own.
Luca Rossi ꩜@lucaronin
After trying literally all the major Twitter scheduling tools, I settled with @typefully.
Killer feature to me is the native image editor — unique and super useful 🙏
Visual Theory@visualtheory_
Really impressed by the way @typefully has simplified my Twitter writing + scheduling/publishing experience.
Beautiful user experience.
0 friction.
Simplicity is the ultimate sophistication.
Queue your content in seconds
Write, schedule and boost your tweets - with no need for extra apps.
Schedule with one click
Queue your post with a single click - or pick a time manually.
Pick the perfect time
Time each post to perfection with Typefully's performance analytics.
Boost your content
Retweet and plug your posts for automated engagement.
Start creating a content queue.
Write once, publish everywhere
We natively support multiple platforms, so that you can expand your reach easily.
Check the analytics that matter
Build your audience with insights that make sense.
Writing prompts & personalized post ideas
Break through writer's block with great ideas and suggestions.
Never run out of ideas
Enjoy daily prompts and ideas to inspire your writing.
Use AI for personalized suggestions
Get inspiration from ideas based on your own past tweets.
Flick through topics
Or skim through curated collections of trending tweets for each topic.
Write, edit, and track tweets together
Write and publish with your teammates and friends.
Share your drafts
Brainstorm and bounce ideas with your teammates.
NEW
@aaditsh
I think this thread hook could be improved.
@frankdilo
On it 🔥
Add comments
Get feedback from coworkers before you hit publish.
Read, Write, Publish
Read, WriteRead
Control user access
Decide who can view, edit, or publish your drafts.
Whenever I hit a problem with React its because I don't have a solid understanding of how it really works.
Here's a brief explainer:
To understand how React works we actually need to understand the problem it was designed to solve.
Imagine it's 2013 and you want to make a banner appear when a user clicks a button just using JS.
You need to do three things
- listen for an event on the button
- find the place in the DOM you want to add the banner
- create the banner and update the DOM at that point.
Here's the catch - every time you update the DOM it causes a UI reflow as the browser paints the new tree structure.
These reflows are a little bit slow so you want to keep them to a minimum.
But in an app with lots of interactivity you don't have any control over when and how often these reflows happen.
Two reflows could happen one after the other and lock up the UI momentarily.
React has a clever solution: it stores a copy of the DOM in your browser's memory.
This is referred to as the virtual DOM and it is the core of what makes React (relatively) fast.
Any changes to your app are captured by React and applied to this virtual DOM first.
These changes are fast because they are happening virtually and not causing any UI reflows.
React then compares the new version of the DOM to the current version (still happening in memory).
This process is called diffing and they use a whole bunch of clever tricks to work out what exactly has changed.
Each part of the tree that has changed is marked as dirty and typically so are all of its children.
These changes are then all batched together and applied at once.
The beauty here is that only the necessary DOM updates are made and they are made at a reliable point in the cycle.
But it isn't magic.
One pitfall is that you can occasionally do things that unintentionally mark components as dirty causing whole portions of the tree to be re-rendered unnecessarily.
This might not seem like a big deal but remember that this virtual DOM creation process re-executes your components.
Function calls, variable declarations, looping over arrays etc all gets re-executed.
This performance hit adds up over time in a "death by a thousand paper cuts" sort of way.
This is why we have tools like memo in React - they provide more information to React about whether a certain component should be updated
Other frameworks like Svelte and Solid just opt out of all this hassle by not using a virtual DOM at all and instead using some compiler wizardry.