How are you dealing with character encoding? I uploaded a CSV file that has an utf-8 character in the name of a column, and in your import flow, under "File Columns", the column name appeared incorrectly encoded (i.e. it's been latin-1'ized)
My file is most probably missing the UTF-8 BOM. I'm not sure what a good option is here.
Have an advanced setting for Sheets (on your site) and pre-set the uploaded files' encoding?
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.
A good place to start with pricing is tiers at $49/$99/$249.
(As recommended in Jason Cohen’s classic and awesome talk “Designing the Ideal Bootstrapped Business”: https://youtu.be/otbnC2zE2rw)
Customers at very low price points (such as $9/month) tend to churn quickly, and, counterintuitively, send more customer support interactions per customer than at higher points. You’ll never earn enough from them to cover your customer acquisition costs.
Getting rid of the cheap plan also removes the, shall we say, more difficult customer.
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.
I also think you are undercharging for a very useful product.
The utility of what you are offering is significant. If I'm a 'cost conscious' startup and I need CSV upload functionality then I either write the functionality myself (30+ hours of dev time + ongoing maintenance?) or I use your service.
If the product works as advertised, you could charge $19/month for a basic plan and that will always be better value than 30+ hrs of time a developer will have to put into the CSV problem with all its annoying edge cases.
My suggestion is to modify the free plan such that users can upload 10k+ rows per upload, but only 20-30 times per month. Then your 'cost conscious' startup with only 5 customers can test your solution, know that it works for non-trivial amounts of data, and happily fork out $19/month when they hit 20+ customers a month and become less 'cost conscious'.
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
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!!!