ronodi

Well we want to reward our early adopters and beta testers.

The initial launch is scheduled for early in the summer.

Our initial release comes with support for Shopify, following Bigcommerce and later on addig support for custom integrations like Magento.

Custom integration is on the road-map but will take us a while to get there. We are still working on our pricing plans, but we want to keep it fair and easy for our users so at this moment we are going to have 2 packages. Also early adopters will have a a more personalized package.

we have a schedule to launch the product early in the summer. our initial target is to integrate with the Shopify platform.

Getting everyone on the same page and making sure that everyone stays that way, is a key thing to consider when building products.

Regarding to development it depends on your needs and how mixed is your development environment (is everyone on a Unix system, or you can have Linux/Mac/Windows)

If you are concerned about mixing you binary with source in a repo you can always use `npm install --ignore-scripts` this should download modules without building them and add them to your repo afterwards, followed by a `npm rebuild` and adding created files to `.gitignore`

For the pre-deploy preparation what I'm doing now is preparing everything in a separate location (pre-deploy path), pulling new code rebuilding it if necessary, running tests if all went ok the code is moved to the final deploy path.

Thanks. I myself use Windows and lots of projects I worked on are running Debian in production. There were a few times you can see the bad side of it, but it always depends on your needs. A quick example would be with sqlite on windows and unix, but this is solved with pre-deploy preparation. Remember that we are talking about production and not development.