AJSturrock

Thanks for all of this, really appreciate the detailed feedback and the links, will check those out.

Apologies about the drum hit at the start! Appreciate that is probably way too loud, especially on headphones. Cutting the first second out now and also adding a fade in for music track on the menu music to ease you in!

The tileset/isometric mismatch and the pixel grid fringing are both great calls. I am by no means an artist so this is a big help! I hadn't come across Unfake before, that looks super useful to clean up the existing assets and any new ones I generate.

I came across https://www.pixellab.ai/ today when I was researching unit sprite animation & tileset generation and think I may have to redo a lot of the graphics entirely, seems to be the most expensive part outside of the Claude Max plan..

Running through your suggestions with Claude now to get them implemented. Cheers!

Hey all, Adam here - founder of Order Legend. Great to see you stumble across our app! :) Let me know if you have any questions, happy to help!

Looks super simple and nice to use, great for those working with the JAMstack building a custom experience! What are your plans for this going forward?

I’ve had some space and time to reflect since moving on from Moltin (headless commerce platform & API recently acquired by Elastic Path). I recently wrote an article where I shared some of my observations and learnings over the past 7 years and layout where I see the future landscape of eCommerce and headless converging 2-5 years from now. It seems to have struck a chord with other thought leaders on Linkedin over the past few days so thought others might find it useful here. I think there may be some takeaways for everyone in the commerce/headless space that reads this, whether you're an online retailer/brand evaluating software solutions, an analyst, consultant or developer, a headless commerce platform delivering services or even more broadly in the software space.

Hey! one of the founders at Moltin here. Thanks for the mention @blackdogie, always a nice surprise to stumble across! Coredna looks interesting (nice explainer video!).

@jsntrmn we often see the need to de-risk technology choices for decision makers at larger retailers which can sometimes be in conflict to what a developer looks for when selecting a tool or service. We're trying to get the right balance at moltin as we think both voices need to be at the table.

Happy to chat with either of you if you would like to share learnings/experience or if I can help in any way, just drop me a message adam@moltin.com

If you want a basic site quickly, then going with a platform like WooCommerce and an off-the-shelf theme may work well for you. Once you start customising themes and adding advanced functionality, complicated folder structures and functional programming styles can cause no end of problems for many developers.

API based means you’re not locked into a specific CMS or blog platform, you’re not even locked into a specific language or device. All we care about is data transfer and logic, leaving you free to do anything with the frontend.

If you want to know more about what our platform provides apart from rapid development, we’ve touched on them in our other comments.

There’s two reasons behind the way we’ve structured our pricing:

Firstly you can very easily circumvent our checkout flow as we don’t lock you into using the entire system, we could therefore be supporting a large store and never receive a payment.

Secondly we see transaction fees as penalising you for selling well. It’s tough to push a product when gateways already charge for payments. A combined total of 5%+ for every order would be difficult for store owners to swallow.

We decided that offering a free tier and flat monthly fees for our paid users would be more acceptable. As a user you know exactly what you will be charged for each month.

Thanks for the feedback though, we’ll see what we can do to explain API requests and storage better.

Firstly we’ve looked at all of these options and as developers got pretty excited by their potential. The problem was that we found them to all be lacking in some degree, Snipcart is only for the most basic ecommerce, Ecwid is focused more on widgets, and Foxycart requires you to use their hosted checkout.

Secondly every member of our team has been in a position at some point in their working lives where we’ve had to build applications that support all manor of strange legacy requests. We completely understand.

Yes, if you use our javascript SDK with the API, you would require javascript for it to work. That said, you could take the backend approach and then there would be no issues with supporting older clients or applications as it would all be handled by the servers.

We have been thinking about adding a hosted checkout page for exactly the reason you describe. it would probably be an option so that you can either use a hosted checkout page quickly, or if you want more control you can use one of our SDKs and build your own checkout.

Thanks for wishing us luck!

One of the biggest problems we faced from the offset was optimising our PHP codebase and to get the best response times possible.

There was only so much we could do before we hit the limits of the existing system, and turning to HHVM really helped to push our API further.

Here's some simple benchmarks we did whilst we were optimising: http://i.imgur.com/vFOXWfl.png

Nice, if you have any questions or need any help just let us know!

Please let me know what you think about this, we're open to feedback!