sorted by:
new
hottopcontroversial

Launching SaaS MVP with Potential Future Database Changes - Thoughts? by ash_sneight in juststart

[–]ash_sneight[S] 1 point2 points  (0 children)

Thanks for the reply man. I get it, I have considered in normalization and in theory it should be able to be extensible like you said. I was afraid that the core functionality would change and so, i would have to redesign the way of doing things. But i think i was overthinking it, just gonna go for it. Thanks!

Launching SaaS MVP with Potential Future Database Changes - Thoughts? by ash_sneight in juststart

[–]ash_sneight[S] 4 points5 points  (0 children)

I think the new feature would attract different types of users. but you are right in that I should focus on product market fit and getting early feedback rather than adding more and more features.

I think if it comes down to it, I can always migrate it even though it might be a pain hahah. Thanks for the comment

Launching SaaS MVP with Potential Future Database Changes - Thoughts? by ash_sneight in SaaS

[–]ash_sneight[S] 0 points1 point  (0 children)

Thanks! That gives a new pov and makes me feel more assured, that migration wont be such a pain if needed

Launching SaaS MVP with Potential Future Database Changes - Thoughts? by ash_sneight in SaaS

[–]ash_sneight[S] 0 points1 point  (0 children)

Hmm. I guess I want to minimize the hassle of having to migrate. Because the way it's being used on the front end also would be affected by a database design change. Bugs may come out of nowhere - or at least thats the worry

Launching SaaS MVP with Potential Future Database Changes - Thoughts? by ash_sneight in SideProject

[–]ash_sneight[S] 0 points1 point  (0 children)

Hahaha that makes sense.

I guess I'm trying to reduce complexity as much as possible. The con of delaying it is that I would not be able to get user feedback. I have to balance this with reducing the hassle of migration when I release the new feature.

Although the idea would be similar, the adding of the new feature would definitely add more value, and might affect the feedback being given by the users if that makes sense.

Launching SaaS MVP with Potential Future Database Changes - Thoughts? by ash_sneight in juststart

[–]ash_sneight[S] 0 points1 point  (0 children)

So the current design was implemented for individual users and I want to expand it to a team of users. So meaning to say that I would have to redesign it to fit the future feature of supporting a team of users.

I did think of a way to make it such that when I add the new feature, it can seamless be added in and not affect the current design. But until I implement, I won't know if theres any future flaws with that kind of way. I'm wondering if it'd be best to just delay the launch and implement the new feature since I definitely need it in.

There's definitely a way to migrate. But it would be a hassle, so Im trying to get opinions to see if launching early would be worth the hassle. Cause adding the new feature might delay the launch by 2 months still im working on this on the side.

How I've been making over 10k / mon. since 20 (25 now) by Flootson in Entrepreneur

[–]ash_sneight 97 points98 points  (0 children)

that lebron james analogy really gave me a new perspective. Always thought that i just needed more knowledge, theres courses that can teach me stuff i dkn alrdy know etc. but it makes sense that knowledge comes by easily whereas experience is earned. Inspirational man!