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.
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.
Great communication skill is essential in making an optimal technical decision.
Behaviour-Driven Development (BDD) is a tool that can help teams communicate better.
Let me tell you a short fiction about how BDD helped a team succeed:
In the beginning, there was a team who were building a product that will make millions of pounds.
Let's call that team Granola, because who doesn't like good old granola?
They struggle to deliver as the product should submit data to the legacy system at the backend.
Given the legacy integration challenges, a new architect was hired to help Granola tackle those complexities.
They were sitting in their ivory tower, observing and collecting information. It's a big enterprise after all.
One day, the architect decided to soar and strike up a conversation with Granola's PM to solve the integration challenges.
Architect: So, would you like the system to be synchronous or asynchronous?
PM: What do you mean by that?
Architect: Is the form sync or async?
PM: š§š
<Long discussion>
PM: Let's reconvene in a week.
Another week passed, and it was time to soar.
Architect: Give me your decision. Is it async or sync?
PM: I, uh, I'm not sure if that's a product decision, to be honest.
Architect: But I need to know if it's going to be async or sync to architect this product.
PM: š¤š
These types of conversations went on for weeks. Poor Granola. By now, they are blocked and unable to move ahead.
Is it going to be sync or async? It's all a mystery.
In all the frustration, the famous Cucumber Newsletter landed in the architect's inbox.
The newsletter introduced BDD. It talked about how it has saved some communication costs in Gherkin Ltd. It showed how communication can be easier when a Given/When/Then language is used.
That looks extremely simple, the architect thought.
Let's give it a go, it's time to soar again.
Architect: *Given* that the form has been filled out. *When* the button is clicked. *Then* what do you expect to happen?
PM: I expect the data to be readable in the legacy system.
Architect: And *Then* what happens to the form?
PM: I would expect it to show that it's been successful.
Architect: Do you expect it to show the submitted data in the table below immediately?
PM: Oh yes, of course.
There are sparks in their eyes now.
The PM thought, finally, this person is talking in human language.
The architect thought, finally, the PM is making a decision.
Architect: *Given* that the form has invalid data, though. *When* the button is clicked, what *Then*?
PM: It immediately shows an error.
Architect: That's expensive. How about we *Then* send an email instead? Here are all the options I can think of ...
<Productive conversation>
A month has passed. Team Granola is now collaborating really well with the architect and delivering at a steady pace.
Every time something is not clear, they would sit together and talk in the Given/When/Then language, even writing it down for a shared understanding.
Even better, the developers are now taking what's been written down as an inspiration for their tests.
And they lived happily ever after.
The moral of the story:
ā BDD is a communication tool that's useful in a certain context.
ā BDD is a silver bullet, adopt it, and all your problems will disappear.