113 karma · joined July 21, 2015
We are not using webworkers. Instead first we upload the files to our backend and then push them to the destination app.
I will get the bugs fixed.
I have also noted down the suggestions on column name and Keypress. We will implement them soon.
Pricing restructure is also on the cards.
Once again, thank you!!!
We will surely have a relook at the pricing model.
To be honest, we haven't thought about the possibility to work everything client side. Its an idea worth exploring.
Our aim is to integrate the importer with multiple destinations such as databases (MySQL, PostgreSQL, S3 etc), APIs (custom, Zapier, GSheets, Airtable) and others (FTP, Email etc). Coding server side would be easier and faster.
Moreover we plan to introduce on-premise deployment options in the future.
What according to you should be the minimum pricing tier?
You can configure the validation criteria for each column via the app admin. Simply mark the column as 'not required' to accept empty values.
I have noted down all your feedback for fast implementation.
Cant thank you enough!
This is our introductory pricing that will evolve over time. Here is our dilemma - on one hand we want to target indie developers, side projects, bootstrapped startups (that are cost conscious) and on the other hand we want to maximize the earning potential and also not look like a low value product.
Making the entire window a drop target is a neat idea. I am noting it down for implementation.
We'll take on this once we hit a few milestones.
We plan to add advanced validation capabilities as and when we get use cases demanded by real customers. Its a huge project in itself!
Thanks once again!
I completely understand your position. Self hosted version is in our long term development pipeline.
Data security is important to us. We have the option to get the data deleted as soon as it is pushed to your app. Please check our note on user data - https://help.csvbox.io/legal/data-policy
Currently, the widget does not support images. Honestly, we havent yet thought about it. Now that you have raised this point, we will surely discuss it.
The validation rules for any sheet can be controlled via the admin dashboard. You can choose to mark any column as required/not required.
To demonstrate the validation capability we enforced 'required' validation on the 'Age' column in the demo.
I am adding all of the 6 points that you have raised in our roadmap to be developed in the near term.
Currently, once the users upload the file, they have the option to delete any rows that they do not want, by clicking the remove button in the widget itself. Once the data is clean they can submit the file.
Your point is well taken. We will upgrade in the future.
1. We are focused on indie developers and startups. Our pricing is reflective of that. 2. csvbox is a no code widget. The entire column model and validation requirements can be defined in the app admin without the need to write a single line of code.
PapaParse has no built is validations. With csvbox you can define a data model in the admin. The users can match columns, validate data and submit the file without you having to write a single line of code.
We will soon be introducing plans with higher row limits as well.
1. Escaping in csv 2. Month names will be treated as string.
This has got us thinking for more such scenarios. Thank you!