I was thinking to make a web app for my college project. Can you please help me with some inspirations for my project ? :P
Things to Know When Making a Web Application in 2015
161–170 of 186 posts
Re: Things to Know When Making a Web Application in 2015
#162>If you can get away with it, outsource identity management to Facebook / GitHub / Twitter / etc. and just use an OAuth flow.
Has anyone built a lasting stand-alone business that relies on Facebook, et al for identity management?
Re: Things to Know When Making a Web Application in 2015
#163This is a bit of a pet peeve of mine, but that banner image is 10 megabytes, it can be compressed down to 2mb without any perceptible loss of quality. Heck it could probably be shrunk further if you can accept a bit more loss because most of the image is blurry and noisy anyway. heres a compressed version: https://www.dropbox.com/s/bw606t7znouxpj1/photo-141847963101...
Good catch. That is ironic on so many levels. I mean there is even a section on "UX: Bandwidth"... Maybe the author should brush up on image compression best practices and consider adding a subsection on images and other media. EDIT: Realized my previous wording was probably a bit too harsh considering the author is still relatively new to web development.
Hard not to catch it when its loaded in progressively on a 20Mbps connection :P. Websites are way too fat these days.
Re: Things to Know When Making a Web Application in 2015
#164This is a bit of a pet peeve of mine, but that banner image is 10 megabytes, it can be compressed down to 2mb without any perceptible loss of quality. Heck it could probably be shrunk further if you can accept a bit more loss because most of the image is blurry and noisy anyway. heres a compressed version: https://www.dropbox.com/s/bw606t7znouxpj1/photo-141847963101...
10 meg? 4k is all the rage now on mobile. just taken a chunk out of someone's download quota with that nice background!
I've been thinking of developing a proxy that compresses responses and forwards them to you, specifically to handle sites not optimized for mobile. There are already solutions like this but I think a self hosted version is what people need.
Re: Things to Know When Making a Web Application in 2015
#165Earlier quoted context omitted.
10 meg? 4k is all the rage now on mobile. just taken a chunk out of someone's download quota with that nice background!
I've been thinking of developing a proxy that compresses responses and forwards them to you, specifically to handle sites not optimized for mobile. There are already solutions like this but I think a self hosted version is what people need.
This one has been around a long time:
Re: Things to Know When Making a Web Application in 2015
#166Earlier quoted context omitted.
> Your use of the term 'probably' suggests to me that you have not run any actual metrics. What I really meant is that if you have a significant non-JS-supporting visitor base, you almost certainly already know it. There are a huge class of web apps that simply do not have to worry about it. If you know who your customers/visitors are then you should already know how important it is to support non-JS browsers. > Requ…
> JavaScript is an integral part of the platform that is the web, just like HTML and CSS I always think it's interesting when people bring CSS into this, because it's actually a very strong counter to the general argument. By design a user agent is well within its rights to completely ignore any stylesheets attached to a page, and the idea was always that this should be completely OK, partly because you have no idea…
> By design a user agent is well within its rights to completely ignore any stylesheets attached to a page, and the idea was always that this should be completely OK, partly because you have no idea what the UA's capabilities are, up to and including whether or not it's doing any kind of visual rendering at all.
I think that is just an outdated idea that does not apply to highly interactive, long-lived web applications. The user agent is well within its rights to ignore anything it wants, of course, but the user agent is not owed anything by the server. With CSS, or JavaScript, the app may just not work.
Re: Things to Know When Making a Web Application in 2015
#167Earlier quoted context omitted.
> JavaScript is an integral part of the platform that is the web, just like HTML and CSS I always think it's interesting when people bring CSS into this, because it's actually a very strong counter to the general argument. By design a user agent is well within its rights to completely ignore any stylesheets attached to a page, and the idea was always that this should be completely OK, partly because you have no idea…
> By design a user agent is well within its rights to completely ignore any stylesheets attached to a page, and the idea was always that this should be completely OK, partly because you have no idea what the UA's capabilities are, up to and including whether or not it's doing any kind of visual rendering at all. I think that is just an outdated idea that does not apply to highly interactive, long-lived web applicatio…
> With CSS, or JavaScript, the app may just not work.
When it comes to CSS, generally most apps will continue to work even if the CSS is simply ignored.
Because that was one big point of CSS. Separation of presentation from content and function.
It's funny. That kind of separation of concerns is something developers talk about valuing, but the SPA/webapp craze erodes the user-facing aspect of it, even while developers are very proud to demonstrate they're thinking hard about which specific kind of separated-concern architecture they're working with well away from the boundary where an outside user or UA would care.
Re: Things to Know When Making a Web Application in 2015
#168web2py is a batteries-included framework that has all of this and much more done for you, tested and proven over many years.
Re: Things to Know When Making a Web Application in 2015
#169Earlier quoted context omitted.
I've been thinking of developing a proxy that compresses responses and forwards them to you, specifically to handle sites not optimized for mobile. There are already solutions like this but I think a self hosted version is what people need.
This one has been around a long time: http://www.khelekore.org/rabbit/
thanks!, That will definitely help a lot. I was thinking of using squid proxy and writing some custom handlers, but this helps a lot.
Re: Things to Know When Making a Web Application in 2015
#170Earlier quoted context omitted.
Can you explain why OAuth is not for authentication? What does it not do that you expect an authentication system to do? What is fundamentally wrong with every site that allows me to sign in with a github/google/facebook account (via OAuth)?
> What is fundamentally wrong with every site that allows me to sign in with a github/google/facebook account (via OAuth)? That is a inaccurate statement. Those sites allow you to login with your Github/Facebook/Google Accounts. That isn't OAuth. Those sites also use OAuth in order to let 3rd party applications access the users data stored on that system. Take this Scenario Alan has a service that finds funny tweets.…
but the email ID he used to register at Twitter is also one of resources associated with his account and can be accessed as Twitter Data?
(beginner here, trying to understand why not use OAuth for Identification/Authentication)