markdown guide

I'd say the main steps when starting were identifying the market's need for the product. To some extent, I satisfied that need by exploring alternatives for another project / discovering their complexity and cost.

As for how I decided to develop it, I knew I wanted to use my current Laravel stack as it would allow me to prototype / get something completed faster. This was proven by the app being built in 9 weeks.

Yes, I'd say a MVP was the starting point. I then brought in a few testers to review and recommend new features. These were added and ended up vastly improving on the original functionality.

I'm not entirely sure what you mean by your last question, but I think the most important thing is to listen to the needs of users. Some may be way off topic / not useful for many people, but most ideas tend to be of use, so be sure to consider them all.


If you're interested in learning about what Pulse is, and what it can do for you, check out the site below. We also have a referral program where you can a 30% commission by referring friends, colleagues or followers to sign up and use the platform.


And if you're feeling so inclined, I'd love an upvote on Product Hunt: producthunt.com/posts/pulse-ed0252...


what was the main steps when starting Pulse ?
how did you decide do develop this product ?
what was the method when starting ? creating a MVP to iterate on the main features ?

I'm working as a dev but closer to the user and its requirements,I'm wondering what change in the way you're coding when you're working with a deeper product . I'm not sure to be clear


Hi there,

What referral software are you using?