[pupdogg]

Overall, very simple and to the point but not worth $219/mo. In your DEMO, the "Order Status" page takes approx. 4.76s to load 205 orders...this seems like a very poor architecture decision or a poorly written SQL statement combined/rendering logic, especially in 2020. You are headed in the right direction though! To compete with the big guns, you'll either need better pricing or better features (including what others already offer). Make sure to do your market research beforehand or lineup a paying customer in return for significant discount. Best software is created when you have end-users using it and providing you direct feedback.

[bhdzllr]

Thank you for your feedback. Of course I will check the status page, maybe there is something wrong with rendering.

[anitil]

It's worth considering maybe kind of BSing that demo a bit. No need to hit servers etc for just a demo - you just want to give an idea of how it'll work rather than have an actual running demo.

[jhowell]

Is this advice anecdotal or from personal experience?

[LordOfWolves]

Lengthy load times are detrimental to UX. Just look at how people are increasingly less likely to wait for a page to finish loading with every additional second it takes to load [1, 2].

In regards to feedback from users, this is especially true when finding product-market-fit (when an idea actually becomes a business). There’s nothing better than learning what customers who actually use your product want in future releases/improvements. It’s a case of building based off actual demand versus based off a hypothetical in one’s mind (a very common “failing”, i.e. learning experience, for first-time founders). Only when your product grows to the point of attracting potential customers outside your target demographic should you not place tremendous value on every single piece of feedback.

[1]: https://moz.com/learn/seo/page-speed

[2]: https://neilpatel.com/blog/loading-time/

[pupdogg]

personal experience