Re:Ask HN: If you needed a crud app built, how would you bui...
by danpalmer on Monday March 06, 2017 @06:27PM
(#13807048)
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.
Re:Ask HN: If you needed a crud app built, how would you bui...
by brianwawok on Monday March 06, 2017 @09:34PM
(#13807853)
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.
Re:Ask HN: If you needed a crud app built, how would you bui...
by Nilef on Wednesday March 08, 2017 @06:32AM
(#13819569)
I'm guessing Thread?
Re:Ask HN: If you needed a crud app built, how would you bui...
by sixpenrose16 on Monday March 06, 2017 @05:33PM
(#13806692)
+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.
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.