spreadr
Joined 11 years ago
Joined 11 years ago
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.