mattstellisoft
mattstellisoft

Matt Anderson

@mattstellisoft

Founder of @stellisoft , creator of Stellify, a web based IDE that lets developers build modern web applications using declarative configuration

6 Posts 11 Views

  • No matching results...
  • Searching...

/ 255

In response to @peterramsing

Yeah I wouldn't say any feedback you get is useful until you start to get into reasonable numbers to the extent that you can see recurring themes. If you think about the successful products out there that you either don't like or wouldn't consider buying because they have no relevance to you or you don't rate them, then that just goes to show that it's not all that useful to ask random individuals what they think of what you're doing!

I wasn't so much making that original post to determine whether people want to buy into Stellify, I was just testing the water to see if any devs out there want to critique the functionality of the app (even doing basic things like successfully signing in as you are hopefully going to do Peter!)

Back to your app, the deaf community is possibly a good target market but I'm not sure how easy it will be to reach them? How do you go about targeting people that happen to be deaf?

121

In response to @peterramsing

It's absolutely the case that there are web developers that will not see the value in what I've set out there. That's not to say that Stellify isn't for you/ them particularly if they work with Laravel (it is just Laravel in the cloud after all) but that particular benefit I've set out doesn't address a problem they're experiencing at this present moment in time.

Personally, I don't have any issues understanding the problem Audio Brevity solves. It strikes me as a really useful tool and on that basis it's possibly just a case of reconsidering where your target market exists or widening your net when it comes to getting feedback. How many people in total have you put it in front of?

1

25

In response to @peterramsing

Hi Peter, it is indeed an IDE however, when coding, you're creating configuration behind the scenes that makes it very easy to perform say, blanket updates to targeted elements or statements of code (even individual clauses within a statement, it's very granular behind the scenes). The Laravel application that you're building upon is also centrally managed, albeit entirely customisable (where customisation is appropriate and secure). So it's more than just "an IDE". It's eventually going to be a very nice way to develop original, high quality, highly maintainable applications upon the Laravel framework. That's the goal and I hope that's of interest to you. Best wishes, Matthew.

1

60