3 ms·

A very similar-looking product for phone applications, called QuickFuse, is here: http://quickfuseapps.com/ http://quickfuseapps.com/ I think the diagram-as-pr

by pak 13y ago

A very similar-looking product for phone applications, called QuickFuse, is here: http://quickfuseapps.com/ http://quickfuseapps.com/ I think the diagram-as-programming concept has some legs for certain high-business-value, low-complexity applications. One of them is voice applications, and another is probably SMS applications. You can imagine many others: email workflows, document workflows, query tools... It comes down to the age-old problem of how to represent and store logic in a fashion that end users aren't afraid to manipulate. Disclosure: I worked on QuickFuse.

nicpottier 13y ago
QuickFuse looks really nice, congrats! I very much like that you let people play with the interface without signing up, might have to ape that. Where's the pricing though? Obviously we agree visual interfaces have some real advantages, especially for things that are conversations (SMS, Voice, USSD). The real trick is managing to keep things simple as complexity increases. I think the most interesting aspect for us has been to see project owners, the ones who go out to the field themselves, build applications that fit their use cases instead of having the cognitive barrier of communicating their needs to a programmer first. Anyways, fun stuff, thanks for sharing.
ericHosick 13y ago
> It comes down to the age-old problem of how to represent and store logic in a fashion that end users aren't afraid to manipulate. I agree. It's the difference between someone who builds a car and someone who drives it. Building the car using diagram-as-programming is probably going to be complex. Using the car in a diagram/visual environment is, in my opinion, the sweet spot of such systems.
mbesto 13y ago
I had a look QuickFuse. Do you still work on that project? Just some advice - in the pitch quickfuse is addressing business customers, but is littered with technical language (not programming language, but written communication technical people would understand). Quickfuse might want to provide some examples of how these business applications get created...for example "this is how a doctor's office sends SMS's" etc
prakster 13y ago
Where is your pricing info?

by pak 13y ago

nicpottier 13y ago

QuickFuse looks really nice, congrats! I very much like that you let people play with the interface without signing up, might have to ape that. Where's the pricing though? Obviously we agree visual interfaces have some real advantages, especially for things that are conversations (SMS, Voice, USSD). The real trick is managing to keep things simple as complexity increases. I think the most interesting aspect for us has been to see project owners, the ones who go out to the field themselves, build applications that fit their use cases instead of having the cognitive barrier of communicating their needs to a programmer first. Anyways, fun stuff, thanks for sharing.

ericHosick 13y ago

> It comes down to the age-old problem of how to represent and store logic in a fashion that end users aren't afraid to manipulate. I agree. It's the difference between someone who builds a car and someone who drives it. Building the car using diagram-as-programming is probably going to be complex. Using the car in a diagram/visual environment is, in my opinion, the sweet spot of such systems.

mbesto 13y ago

I had a look QuickFuse. Do you still work on that project? Just some advice - in the pitch quickfuse is addressing business customers, but is littered with technical language (not programming language, but written communication technical people would understand). Quickfuse might want to provide some examples of how these business applications get created...for example "this is how a doctor's office sends SMS's" etc

prakster 13y ago

Where is your pricing info?