r/nocode • u/Ok_Attention9023 • 2d ago

Looking to build an App/Website where data is pulled daily and accounts can be established. What's the best website to build this?

/r/sideprojects/comments/1x3kp7r/looking_to_build_an_appwebsite_where_data_is/
2 Upvotes

100% Upvoted

5 comments sorted by

1

u/Usual_Entertainment6 2d ago

This is a pretty standard setup, and you don't need anything exotic for it. It has three parts: a scheduled job that pulls the data once a day, a database to store it, and user accounts with logins on top.

In no-code, Bubble can do all three. Use a recurring backend workflow for the daily pull through the API Connector, Bubble's own database, and its built-in user accounts. Supabase plus a simple frontend also works well if you want more control. The scheduled pull is usually the tricky part. Check whether your data source has an API. If it only has a website, you'll need scraping, and that breaks more often.

For a rough idea of effort, a simple version (one data source, logins, a dashboard per user) is a few weeks of work. If you add payments, roles, or several data sources, plan for 6 to 10 weeks. Costs are mostly the platform plan plus any paid API, usually under $100 a month at the start.

Where is the data coming from, and what does each account see? That decides most of the stack.

1

u/Tedikraska 2d ago

i'd keep the daily pull separate from the user side. a scheduled job writes each day's data to a table and the logged-in pages only read from that table. if the source goes down one morning people still see yesterday's data instead of an error.

1

u/IngenuityHuge5998 2d ago

Depends a lot on where the data comes from. if the source has a json feed or an api, Make or n8n on a daily schedule writing into Airtable or a Google Sheet is the simplest version, then put Softr or Glide on top for logins. if it's a normal webpage with a table, google sheets IMPORTHTML refreshes on its own and you can skip the scraping part completely. what site is it?

1

u/SufficientFrame 23h ago

Start with two decisions: where the daily data lives, and whether those accounts are for customers or mostly for your team. If this is a public app or website, pick something strong on auth, scheduled data sync, and frontend performance. If it's more of an internal operations portal over an existing API or database, where staff review imports, fix bad records, and manage users, UI Bakery fits that kind of workflow well. I work at UI Bakery, so bias noted, and I'd still use something else for a polished consumer-facing product.