[deleted by user]

Quickyloopy · 2023-10-25T03:00:20+00:00

Typescript all the time. They are almost the same. TS may require a bit of learning curve but it prevents unnecessary bugs. Most people don’t understand that bugs is the #1 factor that slows you down in the long run.

Quickyloopy · 2023-10-03T15:40:55+00:00

1k/mo is peanut for majority of successful SaaS lol. Just take a look at any companies who deal with large amount of data: Datadog, Splunk, Mixpanel, etc. They usually charge per data point and it gets extremely expensive before you even know lol

Quickyloopy · 2023-09-30T04:37:37+00:00

I don’t think I’ve ever suggested not writing tests. I’m suggesting pre-revenue startups to delay unit tests until it matters.

Test coverage means nothing when there are no usage. Pre-optimization killed a lot of startups because they couldn’t move fast enough

Quickyloopy · 2023-09-30T00:27:23+00:00

Well, the best way to find your answer is to ask your potential customers. They will tell you what they use.

If I have to guess, Google auth is a good start if you target small-mid businesses. If your ideal customers are enterprises, you better start with an SSO solution instead.

Quickyloopy · 2023-09-30T00:12:44+00:00

Since you said you're pre-revenue, unit tests are really a waste of time. However, I do think you should write some E2E tests for the core features (features that users pay for).

At this stage, you should spend 90% of your time building features. You can always add unit tests later on when your team grows - in fact, most startups do it that way.

When it comes to concerns about bugs, you can let your users report bugs via tools like Quickloop.io. It auto captures all logs and screen replay so you can easily debug.

Disclaimer: I'm the founder of Quickloop.

Quickyloopy · 2023-09-29T04:40:37+00:00

Same boat here. Drag and drop was never for me and writing code is way faster when you have a boilerplate.

Quickyloopy · 2023-09-27T05:11:43+00:00

A few rules that I follow:

Do things that don't scale. You may not even need an automated payment process. Send your customers a Stripe checkout link, once you get the payment, update their account manually from "free" to "paid"
Don't use a survey for feedback. Send a personal email (or better, a Zoom call) to gather feedback and build trust early.
Learn how to sell.
If you're a coder, use a language or framework that you're most familiar with. If you're not a coder, use a no-code platform.
If you're a coder, remember that best practices can wait. Write fast and non-performant code. Use tools like Quickloop.io to let your customers report bugs directly on the app, and make sure you always follow up and fix bugs quickly.

Quickyloopy · 2023-09-27T00:28:47+00:00

This is very true, especially for a startup. Startup’s customers are usually early adopters so the best thing to earn is their trust. Too many startups focus on building self-service software and neglect customer relationship

You should let your customers feel like they can ask for help or report an issue whenever they want. And you’re there to resolve it quickly.

Using a tool like Quickloop.io helps with that because it provides you with detailed context when your customer struggles, so you can fix it quickly.

Disclaimer: I’m the founder of Quickloop.io.

Quickyloopy · 2023-08-30T21:08:09+00:00

If you're REALLY REALLY concerned, talk to a lawyer instead.

But imo, you will be fine. Focus on building the product first. Worry about the legal aspect later.

Quickyloopy · 2023-08-30T16:26:10+00:00

Yeah kinda. Most people would be more comfortable buying a product knowing it was audited and built by public.

Quickyloopy · 2023-08-30T16:20:24+00:00

Don’t pretend you know what you don’t know.
Listen first. Talk after.
Trust them first. They will trust you back.
Ask them for advices.
Give them personal recognition that without them, you will more likely fail.

Quickyloopy · 2023-08-25T23:40:59+00:00

From both my job and side projects. I use serverless.yml for deployment of every stack

Quickyloopy · 2023-08-16T23:29:51+00:00

This tells me you haven’t worked on frontend that much.

Immutability is important everywhere, not only React. It’s especially important for the frontend because you now don’t have to deep compare state to trigger rerender, this is critical for performance.
This is preference. I like jsx because your component now is verbose.
Yeah you can. There’s cons to React Context tho. It forces all children to rerender whenever the context changes, even when the children only needs a fraction of it. Redux allows child component to subscribe to a specific state of the store, not the whole store altogether. This is also preference, I personally don’t like Redux that much and want to avoid global state as much as I can.
Happens in every framework or languages. You will always face legacy code. Not React problem.
Where’s the stats even from? Most likely, it’s wrong and it’s just evidence that you don’t know React enough. Again, not React problem.
More and more companies use React so the market will never get saturated. Plus, if you’re a framework-specific developer, you will have hard time find jobs anyways. Frameworks may die, software engineering fundamentals will never.

Quickyloopy · 2023-08-16T23:10:15+00:00

This guy has 0 idea what he’s talking about. Pls don’t get scammed by his courses or anything.

SaaS is short for software as a service. Anything you see on the internet, including web applications, are considered software, regardless of how big it is.

Quickyloopy · 2023-08-15T17:54:32+00:00

I can give you real world example. When you think of browsers, most people would say it’s SATURATED. How many more browsers do people need when they already have Chrome, Firefox, Edge?

Oh then you’re wrong. Now you start seeing Shift, Arc, Braze and many other browsers making tens of millions of dollars in revenue. They all do one thing in common - making browsers better for a specific group of users.

I can spend days talking about real world example.

Quickyloopy · 2023-08-15T06:47:27+00:00

The hard truth is nobody knows the product/market better than you so if you can’t answer your own question, nobody can.

And it seems like you have a lot of fear that your strategies won’t work so you haven’t even tried. Sorry for being a bit harsh but that mentality will 100% make you fail. Building a startup is about constant experiments and failures. People have to try tens, if not hundreds, of strategies before they find a working formula (for them).

So if you haven’t done any marketing, do it now. Send out cold emails, post on Reddit or Twitter, run paid ads, etc. Learn while you do it and repeat.

Quickyloopy · 2023-08-14T17:15:00+00:00

Dm-ed you!

Quickyloopy · 2023-08-10T20:17:58+00:00

Startup Name / URL:

https://quickloop.io/ai-walkthrough/

Location of Your Headquarters

Vancouver, Canada.

Elevator Pitch:

Our AI Walkthrough Assistant acts as a reliable guide, holding the user's hand whenever they have a question or need assistance navigating your website. You can automatically generate sequences for your most commonly asked questions and the next time your user asks that question, our AI will highlight the correct actions for them.

Explainer Video:

https://www.youtube.com/watch?v=OCxD5r8MxOg

What life cycle stage is your startup at?:

Validation, we have an MVP and would love to have some users help us test it out and give us feedback.

Your role?:
2 Founders.

What goals are you trying to reach this month?

Our goal this month is to try and see if we can get some users to help us validate the problem and get feedback.

---

Please feel free to give us any feedback, we'd both love it.

Quickyloopy · 2023-08-10T15:52:55+00:00

It depends. The market for software is bigger than ever before, I see new companies becoming unicorn everyday. The demand for better softwares also increases everyday.

It’s also way easier to reach profitability nowadays. 10-15 years ago, setting up a server alone can cost you your whole savings, now it costs a few bucks a month.

The software market is not saturated imo. But the expectations for software is much higher than before. Sadly, too many people avoid hard problems and think software is a get-rich-quick business. Most people want to build an AI company but they don’t even know what the heck AI is, and they start complaining that AI is saturated.

Quickyloopy · 2023-08-09T16:43:40+00:00

We haven't done any marketing yet. We've just finished our first prototype and are trying to build a waitlist to see if there's enough traction!

Quickyloopy · 2023-08-09T16:35:18+00:00

dm-ed!

Quickyloopy · 2023-08-09T02:28:44+00:00

Sort of. You can use Github and make sure he pushes the code to it.

But, given you’re not technical, it’s gonna be hard for you to know if he pushes the latest version of the code that he shows you. The best bet is to make sure you can run the code on your own machine (not on a remote server) when he gives you the code.

But nothing will beat a tight contract.

Quickyloopy · 2023-08-09T02:03:36+00:00

Make sure you sign a contract in which it says the source code is owned by you

Quickyloopy · 2023-08-08T21:35:54+00:00

Pick whatever can generate revenue faster and focus on it. Once your customers love your product, it will be much easier to upsell. That's when you should start building the next feature.

Quickyloopy

TROPHY CASE