Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
all the functional parts are server calls, app or website. all of them. buying a ticket involves authenticating with both the owner’s server and my bank. that’s a network thing. can’t download my ticket til I do that, site or app. even looking at a timetable (i dont see where in the app I can do that? but point to point trips) on the app doesn’t work when im in airplane mode, but I know for a fact my browser caches, and if I’ve looked recently or left the page open, it will still be there when I come back.
there’s no advantage of an app, unless you’re doing fancy graphics shit, which eats battery like a mother fucker and makes low end devices much more unhappy.
Sounds like you’re talking about a train app or something. I’m talking about an info/tourism app for a historical cemetery, where there’s lots of potential for multimedia.
But uh, yeah, thanks for the beginners guide to client/server architecture, I guess.
okay I was using a specific example of an unnecessary app I used in the past week. never used the cemetary app, never had to deal with trying to when im outside of network range. still pretty sure it could be a website.
all the functional parts are server calls, app or website. all of them. buying a ticket involves authenticating with both the owner’s server and my bank. that’s a network thing. can’t download my ticket til I do that, site or app. even looking at a timetable (i dont see where in the app I can do that? but point to point trips) on the app doesn’t work when im in airplane mode, but I know for a fact my browser caches, and if I’ve looked recently or left the page open, it will still be there when I come back.
there’s no advantage of an app, unless you’re doing fancy graphics shit, which eats battery like a mother fucker and makes low end devices much more unhappy.
Sounds like you’re talking about a train app or something. I’m talking about an info/tourism app for a historical cemetery, where there’s lots of potential for multimedia.
But uh, yeah, thanks for the beginners guide to client/server architecture, I guess.
okay I was using a specific example of an unnecessary app I used in the past week. never used the cemetary app, never had to deal with trying to when im outside of network range. still pretty sure it could be a website.