It is 2016. Development work is pretty much copy and paste instead of rocket science.
Based on this article http://www.recode.net/2016/6/8/11883518/app-boom-over-snapch..., the whole app ecosystem is dying, and less and less people are going to explore new apps. In the short future, people will stop paying the insane amount of money to developers to build the apps nobody is using.
For app development, the hard part has already been done through well-written lib, and the developers mainly write some trivial business logic to put these components together.
When instagram is made there was no library of making actual logic. You should not rely on libraries if you want to make instagram you should rely on people who can make that kind of libraries
I would be "impressed" with your productivity if you write an authentication, message and notification system from scratch over twice, and each time takes over 40 hours.
Why does it take over 40 hours to implement features, which have been implemented for millions of times and have existing solutions and code in the Internet. Authorization (Social and Email) seems to be one or two hours of work with existing solutions.
And you think you can build a great integrated experience that just works with multiple platforms in "one or two hours of work"? Am I right in assuming that you never built systems like this?
I agree, according to the article, the front end of "email authorization" takes the most time to do. For an MVP a login system really just has to work, and then you can personalize it more as you go. Most of the time for an MVP should be dedicated to the main features of app. (In this case uploading pictures, news feed, etc).
For my app we used Auth0 to quickly get login working before we had to present it. It took about total 5 hours to set up and test. Since then we have built our own login system and made sleek looking create/login screens; which in total took about ~15 hours.
Almost everything you mentioned does not make any sense.
1. Search is just not hidden in GUI for users, who are not logged in, but these users can still perform search as other people mentioned in comments
2. Github Search is definitely cached
3. It has nothing to do with DDOS. Do you expect Google requires you to sign in in order to prevent DDOS? Moreover, unless Github is totally wall-gardened, there are tons of ways to DDOS the service. I suggest you need to learn how DDOS actually works.
2. No disagreement that searching for the same thing can be cached. But that's not the problem. Search for "banana" "banana 2" "banana 3", etc. It's very simple for a botnet to hit a search function like this with unlimited variance, making it impossible to cache against.
3. You think that Github and Google receive the same revenue benefits from providing a free search?
That's not necessarily bad. It just means someone thought that it was more important for the interface to be easy to discover than it was to keep it clean.
In my opinion a good IM system needs to be both easy (as it targets a mainstream audience that needs to voluntarily adopt it, a trouble that MS's offerings never had) and powerful (as it quickly becomes a big part of your day to day). Not the easiest tradeoff to design to.
The clear upper hand granted to the former in this product release is pretty telling of Google's conundrum: they need to gain adoption over everything else.
Thanks for suggestion. I have tried to follow the instruction here https://developers.google.com/apps-script/add-ons/publish to publish SheetSQL as an add-on, but I was stuck at step 4, since I did not see "Deploy as Sheets add-on" the option after I performed the previous steps.
I'm not sure. I've also tried to publish an add-on but couldn't figure out what any of it meant. Google Drive and Docs seems to be forever changing the way things work and then only rolling out the features to certain people (to do with geography a/b testing)? It makes it kind of confusing tbh.
