Thread by @SarkisBuniatyan

In March, @KaraviasD and I began developing @Restepio to automate making and learning. We decided to #buildinpublic and aimed to launch on June 1st. We need some more time to polish the experience.

🧵 Here's our journey and what we've learned creating Restep.io

1 - I met @KaraviasD and @Andree_Design last July in Greece.

We started creating the first multiplayer platform for creators called Schema, which led to breakthroughs in automation and our pivot to Restep.io. Clone our @Webflow prototype. webflow.com/website/Schema

2 - Our lead developer @Thanos_ksk snapped his fingers and found a way to automate @Webflow like never before.

We realized we could use this tech to click in your browser and repeat any workflow on your device for you on request. Restep.io was born in March.

3 - The first app we wanted to automate with @Restepio was @Webflow.

We managed to integrate half of it within a week and thought, "How hard can the rest be?" We soon found out our technical approach didn't automate every function correctly or run the same on all devices.

4 - Quick and dirty can end up dirtier than quick.

In the interest of releasing Restep.io's beta asap to get feedback, we made hasty decisions to accelerate development. Shortcuts rarely pay off, especially when developing software. Do it once and do it right.

5 - We ran into fun obstacles. Original ideas lead to original bugs.

@Webflow would slow down if our Chrome extension was floating.

@Webflow's input fields wouldn't accept our auto inputs.

Restep.io worked differently if you changed your Chrome profile!?

6 - We hired talented developers from Nigeria who helped us crush these bugs and upgrade @Restepio's architecture in no time.

More importantly, this helped reinforce our remote culture and expand our multicultural team. @WillOdia @EreyomiO Mubarak Asafa

7 - More people means more opportunities for breaks in communication.

Even the best talent can't do their best work unless you onboard them and delegate tasks correctly. Restep.io grew to a team of seven overnight without structure in place. This slowed us down.

8 - We quickly aligned our team using a small but effective stack.

Knowledge repository, task management, design system: @NotionHQ

Communication: @SlackHQ
Code repository: @Github
Brainstorming: @MiroHQ
Prototyping: @Webflow
Design: @Figmadesign
Marketing: @Twitter

9 - We announced Restep.io in May with a demo to see if the maker community needed our product and the response was a resounding YES.

The signups were rolling in, we partnered with companies, and were getting ready to launch. Every startup knows what comes next...

10 - You can clone Restep.io and our @Webflow demo.

The next version is in development and will also be cloneable.

That is @Restepio's #buildinpublic policy. Please feel free to copy it.

Webflow.com/website/restep…

11 - Towards launch, Restep.io was running perfectly on some devices but not all. The unknown unknowns began stacking up.

So we worked the problem and discovered not only how to stabilize our platform but make it much smarter and unlock new possibilities.

12 - The first version of Restep.io could only blindly repeat workflows.

For example, it didn't understand if a menu was already open. It opened it again either way. Restep can now detect what's going on and what you're asking it to do in @Webflow.

13 - This breakthrough paves the road for machine learning.

In the future, Restep.io will be smart enough to analyze workflows by repeating them and gain the ability to annotate steps, optimize resteps, offer suggestions, create workflows on its own, and more.

14 - We improved Restep.io's UX with a content stream and introduced Recourses. These are bundles of resteps that makers can sell.

We're also building Caption mode, which enables you to read each step that Restep executes and learn as it builds step by step.

15 - Each website has a different structure. Restep.io needs to recognize all the elements in a page to run intelligently.

We're developing a system that displays all the raw elements in any website you visit and enables makers to easily map out every function.

16 - Restep.io will launch with a curated library of @Webflow resteps.

These are projects you can rebuild and workflows you can repeat within seconds. It's pure magic in your browser. Our next version will give you the ability to create and sell resteps yourself.

17 - Restep.io breaks down language barriers.

In Guided mode, Restep indicates where you need to click so you can build and learn with 100% accuracy regardless of where you're from.

@Danachend and I are working to bring @Restepio to China.

18 - We're proud to be working with prolific @Webflow designers such as @josephberry88 to convert their projects and courses into resteps.

If you'd like to bring your workflows to Restep.io, email [e-mail]

19 - Instead of spending thousands of dollars recording lengthy tutorials, companies can now teach you by building with you in realtime.

I'm excited to be working with @LaceyKesler and @ColinWinhall to automate @AdaloHQ. Wait till you see this @David_Adkin :)

20 - We're on track to launch Restep.io's public beta this month but aren't sure how long it will take to receive approval from the Chrome store. We'll let you know once we've submitted our extension.

Sign up for our beta and follow @Restepio. Thanks everyone!