site banner
PaperclipPerfector  1mo ago (text post)   2030 thread views

Small-Scale Question Sunday for March 31, 2024

Do you have a dumb question that you're kind of embarrassed to ask in the main thread? Is there something you're just not sure about?

This is your opportunity to ask questions. No question too simple or too silly.

Culture war topics are accepted, and proposals for a better intro post are appreciated.

1
Top Bottom Old Controversial Comments
Jump in the discussion.

No email address required.

I live in an apartment building that offers free visitor parking with online registration. The web form asks a lot, between the info of visitor and the resident to every detail of the car. It's not unreasonable, but it's time consuming, and there isn't a way to easily re-register a car that's previously been registered.

How feasible is it to create a local app on my Android phone that automates all this?

I did some light coding years back so am not completely code illiterate, but expect will have to heavily rely on GPT 4 / Claude 3 and general smarts to make this work. I feel like the personal breakeven for me is making this work in 8 hours or less. To be honest, I doubt this app will save me more than 4 hours over the lifetime of my staying in this apartment, though the personal satisfaction of beating an inefficient system is worth like 4 hours.

It seems to me like the basic components are:

  • Install Android IDE
  • Tailor an HTTP request to the web form: replicate form submissions, which is pretty basic--visit the URL, enter the static building passcode, choose permit type from a dropdown, then enter text fields, then click submit
  • Create a Google spreadsheet with all the requisite info of my guests and their vehicles to serve as the database. Seems easier to just make the file visible to all with the URL, though I understand it'd be more secure to invest in figuring out their API with OAuth etc.
  • Create a simple app GUI to tap on a name to auto submit the HTTP request to the webpage
  • Create error handling to confirm form returns success

There are probably a dozen QOL features that I could add, like displaying the registration date and time, add/edit guest info directly in app, offline support etc. But I'm just interested in the simple basics right now.

What do you think about this approach? It feels like this is a bigger project than 8 hours (for me). Are there places to cut corners so I can more readily rely on GPT4 to do the heavy lifting?

Separately, I'm curious how long end-to-end you think an actually competent developer might need to create something basic like this. Because if it's like 2 hours with the aid of GPT4, I might try to see if I can pay a friend to do this for me...

Android app? Almost certainly a bad idea, unless you already have experience in building android apps and getting them onto your phone. Just figuring out how to build a "hello world" level app and get it onto your phone could easily take 8 hours by itself, much less setting up even a fairly basic UI that's functional. Using GSheets as a data store sounds like a bad idea too, way too much work to interface with. What I'd do is, in this order, following the steps until you think it's good enough or get tired of it or whatever:

  1. Open up dev tools network tab the next time you use the form. Note down everything about the request to actually reserve a spot and what it returns on success and failure.
  2. Put together a CLI script on your developer machine to make those requests. Iterate on that until you are able to successfully reserve a spot without using the website directly. Doesn't matter what language, Python is fine, just make direct HTTP requests, you almost certainly don't need full browser emulation.
  3. Hard-code in the info for your regular visitors, implement a decent CLI interface to make reservations for any of them. This is probably good enough for most people.
  4. Turn that script into a basic web server, running locally on the developer machine. A few simple HTML pages to interface with it you can use on the browser on your developer machine.
  5. If you still really want to use it on mobile, rework the CSS etc until those pages look good on a mobile browser
  6. You could leave it running on your developer machine or some other machine in your local network and access it from your mobile any time you're on your home WiFi. Or you could deploy it to a proper web server somewhere, probably for free, maybe using Google Cloud Run or something like that, to be able to use it on your mobile from anywhere. It'll be on a weirdo URL nobody can guess, so you can probably get away with no authorization. And the visitors are still hard-coded, so you'd need a redeploy to add or remove anyone, but that shouldn't be hard enough to be annoying.
  7. If you're still feeling ambitious, add a proper DB on the server to store visitor info, and web interfaces for managing them. Probably ought to do authorization too at this stage.
  8. For even more ambition, set it up so other residents can register themselves on your system, enter their own visitor lists, and reserve spots too. Then advertise it to other people in your building, or even people in other buildings that use the same system.

Thanks for the walkthrough! Think you're absolutely right in avoiding an entirely new platform (i.e. phone). Think I'll aim for step 3 on your list. Then maybe before the EOY GPT 4.5's user agent will be able to assist with the rest (like on mobile).

What is this place?

This website is a place for people who want to move past shady thinking and test their ideas in a court of people who don't all share the same biases. Our goal is to optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.

The weekly Culture War threads host the most controversial topics and are the most visible aspect of The Motte. However, many other topics are appropriate here. We encourage people to post anything related to science, politics, or philosophy; if in doubt, post!

Check out The Vault for an archive of old quality posts. You are encouraged to crosspost these elsewhere.


Why are you called The Motte?

A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently, it's an element in a rhetorical move called a "Motte-and-Bailey", originally identified by philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial but high value claim to a defensible but less exciting one upon any resistance to the former. He likens this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired propositions to which one retreats when hard pressed."

On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.


New post guidelines

If you're posting something that isn't related to the culture war, we encourage you to post a thread for it. A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a submission statement. A submission statement is required for non-text sources (videos, podcasts, images).

Culture war posts go in the culture war thread; all links must either include a submission statement or significant commentary. Bare links without those will be removed.

If in doubt, please post it!


Rules


Recommended Posts And Communities

Recommended Realtime Chats