Slobodan Stojanovic

Day 35: Signup Invitations and Analytics

Now that we have a working MVP, there are a few more things to finish before onboarding our first users. First, we can’t open an MVP to everyone. There’s a big chance that we’ll not have many users in the first weeks or months (that’s a startup reality),

Day 32: Demo and Bundle size

After 30 days of working on Knowlo, the MVP is almost ready. There are still some tweaks and updates before launching the MVP, but the tooltips work! Do you want to see the demo? Demo I’ll assume you answered yes 🙂 So here’s the demo!First, here’s the video

Day 29: Svelte Tooltips and AWS SigV4

Slobodan and CofounderGPT connect the Svelte Web Component to API Gateway using Cognito Identity Pool credentials and SigV4, and show a demo of the Knowlo app!

Day 28: Migrating Tooltips to Svelte

Slobodan migrates a Web Component to Svelte with CofounderGPT's help. They also connect the tooltip to the API using temporary Cognito Identity Pool credentials.

Day 27: Building an MVP – Tooltips, Shadow DOM, and Web Components

Slobodan asks CofounderGPT to assist him in writing a Web Component for tooltips, preparing a component for embedding on users' web apps and testing it.

Day 25: Building an MVP – Connecting the dots

On Day 25, Slobodan connects the Create Tooltip flow by writing some React code and an AppSync Lambda resolver with some help from CofounderGPT and Github Copilot.

Day 23: Building an MVP – the Devil is in the Details

CofounderGPT helped me to connect the login and signup flow on Day 21. The progress we made looked promising, and the goal for today was to connect the UI with GraphQL queries and mutations. However, even when the big picture seems clear and promising, many small things can block

Day 21: Building an MVP – signup flow and GraphQL

CofounderGPT and I got stuck on Day 19 with AppSync JavaScript resolvers. Everything worked great until we tried to deploy the app and realized that JavaScript resolvers do not work for unit resolvers! Currently, they only support pipeline resolvers. Resolving the resolvers issue As mentioned in the previous article, besides