Cool, but web apps still can’t do location tracking in the background. So please do tell me how my fitness app should be a web app instead?
App Should Have Been a Website (and Probably Your Game Too)
81–90 of 384 posts
Re: App Should Have Been a Website (and Probably Your Game Too)
#82I'll take a native app over a web app every time.
HTTP was not designed for apps, it was designed for serving HTML. We had a decent solution in Java applets and the tech giants could play nice so we couldn't have nice things.
The work around has been a huge kludge of crap frameworks of the day trying to reinvent the OS and associated API in the browser. It sucks all the way down.
Apps are:
More powerful
More efficient
Have better tooling
Have stable APIs
Are easier to debug
Re: App Should Have Been a Website (and Probably Your Game Too)
#83I'd give anything to move our apps to the web. We're in the medical field (our apps connect to medical devices over Bluetooth), so publishing on Google Play is like a Kafkaesque fever dream. Two days ago they tell us our app fits into categories like:
Activity and Fitness
Nutrition and Weight Management
Sleep Management
Medical Device Apps
So we gotta update our policies, but today they said something like: "Actually, jk, you don't qualify as a Medical Device App anymore - app update rejected."
Meanwhile, Apple (who used to be the actual nightmare) has somehow turned into the reasonable one. They approve apps in minutes now. MINUTES.
It's like Google saw Apple's approval process from 10 years ago and thought, "Let's do that, but make it a circus." At this point, I dream of ditching native apps entirely. Too bad Bluetooth on the web is still a bit... fragile.
Re: App Should Have Been a Website (and Probably Your Game Too)
#84I'll take a native app over a web app every time. HTTP was not designed for apps, it was designed for serving HTML. We had a decent solution in Java applets and the tech giants could play nice so we couldn't have nice things. The work around has been a huge kludge of crap frameworks of the day trying to reinvent the OS and associated API in the browser. It sucks all the way down. Apps are: More powerful More efficien…
> a decent solution in Java applets
Uh!
Re: App Should Have Been a Website (and Probably Your Game Too)
#85I'll take a native app over a web app every time. HTTP was not designed for apps, it was designed for serving HTML. We had a decent solution in Java applets and the tech giants could play nice so we couldn't have nice things. The work around has been a huge kludge of crap frameworks of the day trying to reinvent the OS and associated API in the browser. It sucks all the way down. Apps are: More powerful More efficien…
When HTTP was designed, there also weren't any images, CSS, or Javascript.
Re: App Should Have Been a Website (and Probably Your Game Too)
#86Please stop making web apps, the web is for documents, not to be hijacked by Google in their attempt to wrestle personal computing from Microsoft. This issue becomes even worse if you try to make software that can both be used with keyboard & mouse and on a small touchscreen. With very few exceptions, you end up with something that works poorly with both interfaces, instead of working great on one of them. Trying to…
Yep. And it gets worse. Websites are at least supposedly sandboxed so they are not as much of a risk as running native binaries. But this is getting worse and worse as browsers expose more and more of their host operating system's functionality. The benefits of using a website instead of a native app are quickly disappearing while the drawbacks have only been somewhat mitigated. We're getting to the point where brows…
Mobile operating systems have really good security models, and native apps are even more isolated compared to the websites.
I really wish that we would have similar isolation options on desktop/laptop OSes.
Re: App Should Have Been a Website (and Probably Your Game Too)
#87I generally agree, but not for any critical workflow. You can't easily archive copies of web software. One day any website you rely on could introduce user-hostile regressions or simply disappear. Apps in the mobile ecosystem also have this problem, but at least you can archive and sideload old APKs on Android (for now).
> you can archive and sideload old APKs
Only as long as external dependencies (like APIs) are satisfied.
Re: App Should Have Been a Website (and Probably Your Game Too)
#88Cool, but web apps still can’t do location tracking in the background. So please do tell me how my fitness app should be a web app instead?
Does your app still function if the user disables location sharing?
Re: App Should Have Been a Website (and Probably Your Game Too)
#89Earlier quoted context omitted.
> at Rogue Engine, we’re committed to being the go-to game engine for Three.js and the web and there you go, author has a vested interest in you making web apps.
well the article is well reasoned enough. what I gave up on was finding actual pricing information for this engine. all it say is free if you earn less than 80k... so what's the price please?
https://rogueengine.io/GetStarted says:
Plus $ 20 $ 10 / month / seat Billed Annually $ 120
Pro $ 50 $ 25 / month / seat Billed Annually $ 300
Enterprise $ 90 $ 45 / month / seat Billed Annually $ 540
Each of those tiers has a different "free if you earn less than $xxx" level that I'm not gonna cut and paste. There's a chart with the differences between what those tiers gets you too.
Also:
Can I publish anything I want to Rogue Play?
You're allowed to publish content that is neither sexual in nature or illegal under either UK law and the laws of your country of residence.
What happens to my files if I cancel my subscription?
When you cancel your subscription your files will be locked and you won’t have access to them until you buy a new license. They will be scheduled for deletion in 30 days.
What happens to my files if I downgrade my subscription?
It's your responsibility to free the necessary space before downgrading. Your files will be deleted after 24hs unless you take action.
----
Re: App Should Have Been a Website (and Probably Your Game Too)
#90Whilst I agree with most of the points, author is making here I cannot help but make a small snarky remark that we, as a dev community, have been talking and dreaming about those talking points since the advent of html5 which is roughly 15ys. Marketing and availability, i.e. is it within reach when a customer thinks about it, are core problems needing to be solved.
Who is this unified hivemind dev community you speak of?
[deleted]