47 ms·

I guess I'm the "something else entirely" vote. If it's mostly for internal use, I would shy away on build on a platform stuff, and find a "form builder" type a

I guess I'm the "something else entirely" vote. If it's mostly for internal use, I would shy away on build on a platform stuff, and find a "form builder" type app with web server capability or a web service. Google sheets feels a little light for this purpose, but likely could be done at some maintenance cost as your number of forms grows. The first hit in my search was zoho creator or Airtable (but I know nothing about either) - I was looking along the lines of something like Filemaker for the web. And just to keep growth in mind, be sure to have a way to export the database and form/field content. That way you can keep the option for a more custom build scenario later. Edit: added a google sheets comment.

sixpenrose16 10y ago
+1 We have built a service [0] that just does this type of use case. You can basically built your forms to receive submissions via drag and drop functionality and CRUD is handled by our dashboard at a submission level. You can also integrate with over 500+ external services without coding via zapier. On each submission, you can set to write to Google Sheet or to your CRM. [0] http://formbit.co http://formbit.co
danpalmer 10y ago
Seconding Google Sheets. We have a large and mature codebase, but we're always iterating with new features. These often require data entry by experts in the company (in our case, stylists, marketers, copy-editors, etc), and the first-pass at the CRUD behaviour is usually just a spreadsheet. Everyone understands them, and most editing/coordination is done in a sheet while a developer builds the models and front-end in the main site (Django), then a simple import script using the Python Sheets API sticks all the data in the database in one go. The second iteration is usually a simple management interface of some sort or user-preferences.
- brianwawok 10y ago
  If you already have Django, why not just use Django admin? Give the users a crud app in 5 minutes and skip the import step.
- Nilef 10y ago
  I'm guessing Thread?

sixpenrose16 10y ago

+1 We have built a service [0] that just does this type of use case. You can basically built your forms to receive submissions via drag and drop functionality and CRUD is handled by our dashboard at a submission level. You can also integrate with over 500+ external services without coding via zapier. On each submission, you can set to write to Google Sheet or to your CRM. [0] http://formbit.co http://formbit.co

danpalmer 10y ago

Seconding Google Sheets. We have a large and mature codebase, but we're always iterating with new features. These often require data entry by experts in the company (in our case, stylists, marketers, copy-editors, etc), and the first-pass at the CRUD behaviour is usually just a spreadsheet. Everyone understands them, and most editing/coordination is done in a sheet while a developer builds the models and front-end in the main site (Django), then a simple import script using the Python Sheets API sticks all the data in the database in one go. The second iteration is usually a simple management interface of some sort or user-preferences.

brianwawok 10y ago
If you already have Django, why not just use Django admin? Give the users a crud app in 5 minutes and skip the import step.
Nilef 10y ago
I'm guessing Thread?