giuliano84

Point 3 is spot on. I think it would be a good strategy to avoid expire dates on subscriptions. Producers could take decisions on whether or not keep sending data by monitoring responses on the consumer's target URL.

Another thing that it should be worth mentioning is that some services batch notifications (e.g Facebook Messenger) so that they can send more data in a single POST request.

Yes but that's why you build webhook for, to let people consume your content. I think DX is critical today and big companies can afford to do the heavy-lifting. As I mentioned in the Subscription Expiration paragraph I totally get Microsoft's reason to put a 72hrs expire date on subscriptions but it adds some friction on the consumer side.

True. Also having a sample request at the very beginning is useful so you don't have to find a way to trigger the event by clicking around on the product UI.

Agreed. I believe that AMQP connections are best suited for wide and articulated local environments. Moreover REST HTTP endpoints are today's esperanto :)

Hey guys, Stamplay's founder here!

It's hard to say by a simple landing page but the service looks quite different in terms of offering.

The visual workflow builder of Stamplay is just a fraction of the whole offering and can be used by developers to orchestrate services or build business logic of their apps quicker.

Aside from that we to offer out of the box User authentication and management API, social signup, Data storage API with automatic generation database and REST API on top of the data model you define, Serverless code execution to implement any custom logic (AWS Lambda like), 3rd party API integrations (Stripe, Sendgrid, Twilio, Firebase, AWS SNS, AWS SQS.. and more), Cronjobs, Webhooks, CDN backed hosting for static assets with SSL + custom domain support.

As long as you understand basic RESTful services, JSON and JavaScript you can use all our core API. Modularity is a key factor of our platform and developers can already share "Code Blocks" to add specific features to their apps.

Brightworks seems more close to be an API design tool and to manage it over the time but I look forward to see more :)

When developers meet cats...

At this moment the first one you mentioned, but the second one is a good suggestion. writing it down now :)

Thanks frequentflyeru,

we're foreseeing that need that's why we're evaluating to build something like Divshot architect on our own (or with a partner already providing a similar service like Froont or Webflowapp)

Hi binary,

I got your points. We had a short outage that has been restored in a flash. +90% of our users login with Google so password reset has been developed just to give users the possibility to re-enter and define a new one of their choice.

Hi strick,

here you can switch pricing between plans and currencies https://www.stamplay.com/pricing

currently it's not an automated thing based on visitor's IP since the infos are all there. But I understand that into the product this could be not that nice to see.

Thanks for pointing this out

thumbs up!!;)

Hi Darren,

yes we are aware of the issue and already working to fix it. Thanks for telling us btw :)

So this really depends on how quickly you can do the job :)

Hi Tepix,

thanks for the assessment but it doesn't really means that. We're in the middle of integrating a RBAC logic on the resources while before it was all about setting something as private/public. Since you pointed out the issue I'd like to know more about how you would use such functionality: - explicitly declare if entries can be private/public - define if users can fetch entries that they own/made - any more fine grained logic?

Hi Chris,

ok this tell me that written like that, the features is very misleading. You can ALWAYS retrieve all the data via API on any plan. The data is yours.

The export one is just a commodity to have it formatted on an Excel or CVS file (good for non tech people or for those who dont want to integrate via API to collect data)

Does it makes sense?

Thanks for this comment!

As a Stamplay co-founder, since the thread is getting crowded of many HN users that know this space very well I think that this is the perfect place to share my vision on how programming will evolve

https://medium.com/@giuliano/programming-easier-better-faste...

Feedbacks are welcome!

Yep you're right, that one solve a very specific problem about monitoring resources. We want to empower people to build products in an easier and more efficient way :)

Btw if you need anything special you can always email me at giuliano dot iacobelli at stamplay.com

Hi Amzil, we're rolling out a developer program but at its fist stage it will be only to add (and sell) App Templates. Components are still on us but we will open that too.

Hi Chton,

thanks for the feedback. You can click on the "i" that appears when you move your mouse over a component to get this modal view with the usable triggers and actions. http://imgur.com/EdGf9Hz

Otherwise you can click the info button on the upper right corner of settings view of every component http://imgur.com/UpAcLdk

Cheers

Hi Nico,

thanks for sharing this, as a co-founder, I'm here available to answer to every question :)

It depends from the service, everyone has its own lock-in. With us you own the data and you can take it anytime, the hard part is to code the backend from scratch on your own.

Yes Cheriot, you're probably right but we wanted to keep it easy to understand. How would you change it? Happy to improve it and make it more "best-practice" compliant and then share it here https://github.com/Stamplay/stamplay-foodme

Yes we now, but modern frameworks work with modern browsers. It's a good opportunity to give Chrome a try ;)

Thanks josh, just in case you want to stick to the Backbone that, there is a tutorial for that ;) http://blog.stamplay.com/how-to-build-an-about-me-clone-with...

Went temporary offline, try now :)

Wondering if someone could check on this, I'd love to have some candid feedback on the approach

Glad that you like it! We've just handled the Disconnect problem thanks for sharing this with us :)

Thanks for mentioning it. In order to understand how apps are created we track clicks on that button, we'll handle this problem cause a lot of people use Adblock and similar tools!

the frontend implementation is intentionally super simple but for any question feel free to drop me line :)