These are some observations around the world of developer tools. Right now is an insanely exciting time to be involved in building apps. The barrier to entry is so low and the productivity is so high that new developers are a force to be reckoned with.

I jotted down a few of my world views around. Again these are world views, there’s some evidence in them but a lot is seeped in bias.

  • Modern app developers are not shy from coding backend servers. They want to code it, so long as it’s productive, pleasant and makes them feel good.
  • Node is the future of the JavaScript Community. Whether or not they are in a Node Server shop, all front end react, angular, vue etc.. projects will need Node tooling like gulp, webpack, etc…
  • Developers want to be able to code a backend. They aren’t scared of it either. npm init react-native init ng init. That’s the way people want to get started. Almost all JS tutorials online are framed like this. Dotnet and Kotlin are already doing the init project way of life. As more an more developers see this from documentation, books, and blogs, the harder it is to convince someone that they don’t want init.
  • Unity is the future of C#. New C# server side development will become quieter and quieter. Microsoft’s incredible commitment to TypeScript will eclipse C# from any sunlight. C# is a fantastic language, however the community and ecosystem are shifting away from new projects being written in C#. It’s harder and harder to find exciting developments from conferences focused on C# Dotnet. Unity however, is king of indie game development…
  • Unreal Engine will switch to C# or a similar level language. UE will feel the pressure and begin supporting C#. Bet: UE will support C# (or a similar-level language) then make a better assets marketplace to attract indie gamers. If this happens UE will quickly chip away at Unity due to the higher product quality. If Unreal stays with an anemic asset marketplace with C++, this will probably not happen. I believe this is the key to generating a community.
  • Swift will lose momentum. Developers will no longer accept the slow iteration speed of Swift development and turn to React Native or possibly another alternative technology. Fast iteration of mobile apps without drastic compromise of performance is going to be the key winner.
  • React Native is the future Mobile Development for the next 3 years at least. Companies want faster and faster iteration cycles on getting mobile content out the door. Swift and Java are just too slow to build, deploy, and test.
  • GraphQL will largely replace new REST projects.
  • GraphQL will incorporate Offline First and Real Time Updates in the next year. This will become their flagship feature. The “schema” management benefit will become more of a pleasant feature. Firebase will encorporate this very quickly in their next few months.
  • MongoDB will create a Backend as a Service with GraphQL offline first and realtime capabilities within the next year.
  • Most front end apps will encorporate offline first data stores like redux-offline.
  • As offline first and real time come to the forefront, databases like PostgreSQL, SQL Server, MongoDB etc… will begin to flex their “change notification” APIs.
  • Most developers are not dev-ops people. They just want their apps to work. The general population will understand programming languages, not shell scripts.
  • Github will incorporate continuous integration and deployment to a kubernetes style endpoint. Websites will be automatically deployed from branches.
  • Visual Studio Code will outpace Atom, Sublime etc… and cannibalize on Visual Studio in the development shops.