#Bookmark feature in mailplane 4 Offline#

Having a universal way to jump right to looking at a specific thing is incredible. Users will use things that are good, and not consider or care how it was built. The web should become the dominant platform for building apps.

#Bookmark feature in mailplane 4 Offline#

Service workers give us important things like offline ability and push notifications. Web technology itself is stepping up hugely here as well. Those are just examples of doing a good job on the web. Just looking at audio/video apps, Skype has a full-featured app, Lightstream is a full-on livestreaming studio, and Zencaster can record multi-track high-quality audio. I regularly use apps that seem like they would need to be native apps, but turn to be just as good or better on the web. Sometimes a web app is so good, I wish it was native just so it could be an icon in my dock and have persistent login, so I use things like Mailplane for Gmail and Paws for Trello. Should I use the Slack or TweetDeck native app, or just open a tab? It’s identical either way. Which is better, Sketch or Figma? We judge them by their features, not by the fact that one is a native app and one is a web app. The line between native and web is blurring. New JavaScript accommodates this very well. That piecing together can be done by UX folks, interaction designers, even marketing. Components are pieced together to build what users see. They will probably become the main deliverable. These things are becoming a standard part of the process for web projects. We’re not building pages, we’re building systems. TypeScript also seems like a long-term winner because it can work with whatever and brings stability and a better editor experience for developers. Now they can compete on speed, features, and API niceity. They accommodate the idea of working with state, components, and handling the DOM for us. Ember, React, Vue, Angular, Svelte, whatever. Websites will be built by thinking of what state needs to be managed, then building the right stores for that state. State is the big concept, as we talked about. As I opened with, user expectations, and thus complexity, are on the rise. We got ourselves into trouble by working with the DOM too directly and treating it like like a state store. And I don’t just mean ES6+ has us covered now, but that’s true. New JavaScript is here.Īs fabulous as jQuery was for us, it’s over for new development. Developers are being asked to build very complicated things very quickly and have them work very well and very fast. What websites are being asked to do is rising.

I also talk about it every week on ShopTalk Show with a wide variety of guests, and I get to travel all around going to conferences largely focused on front end development.

I work on CodePen, which is quite a hive of front end developers. Aside from running this site which requires me to think about front end development every day and exposes me to lots of conversations about front end development, I am an active developer myself. If you really needed hard answers to this question, you’d probably look to aggregate data of survey results from lots of developers. I’d say I’m underqualified to answer the question, as is any single person. I was asked to do a little session on this the other day.