Live data from Hacker News

Show HN: Dropbase – Build internal web apps with just Python

github.com

41–50 of 119 posts

Re: Show HN: Dropbase – Build internal web apps with just Python

#42
post #4

Earlier quoted context omitted.

thanks for the feedback! i'm curious, how critical are graphs for your internal tools and what are some examples of their use?

Pretty darn critical! I built a service a few years ago to scrape natural gas volumes from different refineries and my client wanted that data plotted over time. Another project collected and displayed wellhead pressure data. Oh yeah, maps are also super important, and being able to overlay different statistics and or graphics over them.

thank you for sharing! i think we'll get there eventually and add components beyond tables, such as charts and maps. current focus is to get the table+sidebar experience right first. the thing that differentiates us from dashboarding tools is that with us an end user can trigger a task that gets or acts on data (as opposed to rearrangement of existing data on ui).

could you elaborate on cron jobs being a pain point? would you use it as a scheduled task to fetch/prepare data before user logs in or let users schedule jobs on their own to run async? any use cases you could share?

Re: Show HN: Dropbase – Build internal web apps with just Python

#43
post #26

Earlier quoted context omitted.

i second that. for external-facing tools, you probably want something custom, branded, and more flexible. when it comes to internal tools, you typically want something quick to get the job done. at dropbase, our focus was on enabling developers to get stuff done efficiently. we noticed that for 90% of internal tool use cases, you only need a table and modal to get user input. so we focused on developing those. while…

Are you aware how most companies external apps look like? Here's how: They don't. What you compete with, what you have to beat, is not "something custom branded and more flexible". It's nothing at all. Cutting yourself out of that market with a tool that would easily be powerful and user friendly enough to fill this gap does not make any sense to me, if that is in fact your true reason. (And also I don't understand h…

This is actually quite encouraging for us as product developers (although maybe it's not a good thing if end users don't get good tools). It just means there's a lot more room to grow. I wouldn't say we've given up on external, but there's definitely a part of us that's hesitant to communicate the product as a "build anything" app so early. The fact that you think that could actually be an obvious differentiator is quite intriguing and thought provoking. I should do more research and understand the extent to which customers of big companies are exposed to google forms (and similar tools). Maybe we'll discover something interesting in the process. Thanks!

Re: Show HN: Dropbase – Build internal web apps with just Python

#44
post #41

What makes a web app "internal"? Does it mean it's just made to be run on localhost? Does it mean it would not run on a server? How so? Also, why using this vs creating a desktop app? (There are ways to create GUI desktop apps in Python)

I normally understand internal to mean an internal corporate application used by the employees.

Re: Show HN: Dropbase – Build internal web apps with just Python

#46
post #44
post #41

What makes a web app "internal"? Does it mean it's just made to be run on localhost? Does it mean it would not run on a server? How so? Also, why using this vs creating a desktop app? (There are ways to create GUI desktop apps in Python)

I normally understand internal to mean an internal corporate application used by the employees.

correct. internal apps are usually built by developers for internal users. examples include processing refunds, updating customer information, managing user permissions, triggering batch jobs, and etc.

the goal of internal apps is to optimize tasks that are tedious and time consuming, but not too common for an off-the-shelf product to be available.

since the internal apps aren't the main product developers work on in a company, they prefer to build them quickly with minimal resources.

internal tools usually run on a server, as does Dropbase

Re: Show HN: Dropbase – Build internal web apps with just Python

#47
post #45

Did you guys pivoted Dropbase from CSV analytics to internal app builder? Interesting move. Internal.io just sunsetted. Maybe Dropbase has what it takes and finding its P/M fit.

yes, that’s us. glad to see you remember our previous iteration :)

internal app builder is certainly a challenging market to break into, but we believe we have something interesting to offer and are quite optimistic about our approach.

were you a customer of the previous dropbase version (csv to database)?

thanks again for your interest, it is always appreciated!

Re: Show HN: Dropbase – Build internal web apps with just Python

#48
Looks cool! I think there is a huge need for tools like this, especially as AI turns more subject matter experts into programmers who can code a bit of python.

At my company we have recently started using NiceGUI which is a python wrapper for quasars+tailwind and seems like a very similar product. I’ve found it has a great level of abstraction that enables you to do Python only web App development without too much magic, but also lets you sprinkle in some CSS and javascript if needed.

Re: Show HN: Dropbase – Build internal web apps with just Python

#49
post #48

Looks cool! I think there is a huge need for tools like this, especially as AI turns more subject matter experts into programmers who can code a bit of python. At my company we have recently started using NiceGUI which is a python wrapper for quasars+tailwind and seems like a very similar product. I’ve found it has a great level of abstraction that enables you to do Python only web App development without too much ma…

NiceGUI looks interesting, reminds me of reflex.dev a little bit.

what kind of apps are you building with it?

Re: Show HN: Dropbase – Build internal web apps with just Python

#50
I am surprised that lack of control and customizability over the frontend is being billed as a feature.

I've built multiple internal tools like those in the example section, and even with a solid framework like react-admin, one of the first requests you're going to get from internal stakeholders is tweaks to the UI.

It's a myth that internal users aren't as demanding as external stakeholders. If anything, they can be more pushy.

I would not want to launch an internal tool, except as an engineering-only POC, unless customizing the frontend were at least as easy as customizing the backend.

Post reply on HN