SmileBASIC Source App
Root / Site Discussion / [.]
Can you not forget about Windows 10 Mobile?
That's more of a randommousecrap job, since he knows the structure of the database. Unless if we made an app that gets its data from a hidden web browser object, but that would be silly, slow and extremely prone to bugs as website development progresses. It would be nice to have an app!This is very true. We should annoy randommousecrap to make an app, then. lol
The problem is that you seem to have a different idea of what an "SBS App" would entail than randomous does. It's very vague. Not just you, I think everyone has different expectations, and few of them are being stated.
Solutions need a problem, not a dotted outline, and the conclusion I see does not seem to definitely follow from the problem presented (that you would like to see notifications), as websites can generate these: https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web (unless you're on iOS).
Lumage can't read.
So I'm going to tell you why what I think you're thinking of is a stupid idea. (And yes, this has been brought up before.) All it's doing is moving the webpage view from your browser of choice to a different shortcut on your desktop. There is no advantage to a lazy approach like that except mention I heard of being able to receive "push notifications." If you want to browse the web on your phone, you use a web browser. This is not a hard concept. I'm fairly sure, even, that newer standards allow a page to send you your platform-dependent notifications. That would be easy to add, though of little use to most people. Possibly you avoid some amount of resource usage with a stripped view, but you're still using a clunky embedded web viewer. Back here, someone even tried to make that exact crapware. Also, please don't try to run that. I can't think of anything GOOD you would get out of this, besides possibly sadistic satisfaction in making randomous work on something, but I can list a few reasons this is bad. First, by removing a very basic web service from a proper browser and making it a trusted app, you're removing the protection that the browser offers you (as well as other tools of convenience). You no longer have the choice of blocking any popups or malicious scripts that may be delivered through the site, and a whole lot less control over your experience. Admittedly, I haven't researched this, so I don't know to what extent it is valid. Even if you trust us, and the advertising, and your phone, SmileBASIC Source isn't... made for that. We test things as much as we can, and try to respond to all bugs reports, but that depends on you using a decent browser. Whatever your phone happens to have for lazy garbage developers, even if it works, just opens up another very specific set of cases where bad or missing implementations (on the browser's side) make more work that doesn't need to be there. And, right, yes, that's the lazy "embed a browser and stick it on the store." Maybe that's not what you're thinking of. Maybe you're thinking of redesigning the entire interface and making API calls to retrieve our website in a sleek, mobile-oriented way. Two issues. One, that's way too much work for something that, again, is already available to you, and still doesn't give you the performance advantages you think you would get. Two, you don't need an "app" for Lightw8 MetrerialCard7 UI. I find the site to be perfectly responsive as it is, but if this is really an interface idea, you should explain those rather than proclaiming for "an app," which is meaningless.
The problem is that you seem to have a different idea of what an "SBS App" would entail than randomous does. It's very vague. Not just you, I think everyone has different expectations, and few of them are being stated.Push notifications would be perfect for me, actually. While a sleek interface for mobile would be nice, it is definitely not required.Solutions need a problem, not a dotted outline, and the conclusion I see does not seem to definitely follow from the problem presented (that you would like to see notifications), as websites can generate these: https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web (unless you're on iOS).Lumage can't read.
So I'm going to tell you why what I think you're thinking of is a stupid idea. (And yes, this has been brought up before.) All it's doing is moving the webpage view from your browser of choice to a different shortcut on your desktop. There is no advantage to a lazy approach like that except mention I heard of being able to receive "push notifications." If you want to browse the web on your phone, you use a web browser. This is not a hard concept. I'm fairly sure, even, that newer standards allow a page to send you your platform-dependent notifications. That would be easy to add, though of little use to most people. Possibly you avoid some amount of resource usage with a stripped view, but you're still using a clunky embedded web viewer. Back here, someone even tried to make that exact crapware. Also, please don't try to run that. I can't think of anything GOOD you would get out of this, besides possibly sadistic satisfaction in making randomous work on something, but I can list a few reasons this is bad. First, by removing a very basic web service from a proper browser and making it a trusted app, you're removing the protection that the browser offers you (as well as other tools of convenience). You no longer have the choice of blocking any popups or malicious scripts that may be delivered through the site, and a whole lot less control over your experience. Admittedly, I haven't researched this, so I don't know to what extent it is valid. Even if you trust us, and the advertising, and your phone, SmileBASIC Source isn't... made for that. We test things as much as we can, and try to respond to all bugs reports, but that depends on you using a decent browser. Whatever your phone happens to have for lazy garbage developers, even if it works, just opens up another very specific set of cases where bad or missing implementations (on the browser's side) make more work that doesn't need to be there. And, right, yes, that's the lazy "embed a browser and stick it on the store." Maybe that's not what you're thinking of. Maybe you're thinking of redesigning the entire interface and making API calls to retrieve our website in a sleek, mobile-oriented way. Two issues. One, that's way too much work for something that, again, is already available to you, and still doesn't give you the performance advantages you think you would get. Two, you don't need an "app" for Lightw8 MetrerialCard7 UI. I find the site to be perfectly responsive as it is, but if this is really an interface idea, you should explain those rather than proclaiming for "an app," which is meaningless.