Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Try out application insights before hating it.

It's a developers tool



sort by: page size:

It's amusing that you think these apps are developed by people who aren't CS grads that have not been put through the absurd hazing ritual that is the modern interview.

Look at Facebook's monster, for example.

The reason these apps are bloated is because too much attention is paid to basic CS and not enough to engineering.


It is weird to hear developers say this. The tooling around your app is essential to understanding how it runs, why would someone not know this stuff?

The reason you don't like app's developed in a certain technology is because you are a developer. Normal users can't tell the difference, or don't care.

No, I love the insight! Thanks for replying with all this, we will take a look at these things. We've built 15 production apps and we are still learning every day.

That is the problem of the tool developers not of the app developers. For us, it is easy to use.

Which application does not require the support for Creating, Reading, Updating and Deleting something?

Most companies nowadays don't do the "Deleting" part due to analytics.


i have used it. it is easy to learn. certainly no worse than the alternatives.

i get your criticism. but i see that very often. most projects just don't know how to present their apps in a good way. it seems like we are trying to describe apps in ways that we think non-tech people would expect, but we are failing.


Because application developers would like to know how their users are interacting with the application?

Sound interesting, I have been planning to do something like this for a while. In the end, app development is so standardised that I don’t get why tooling is so terrible.

It sounds like you saw some great apps using the right tools to solve the problem space and then you saw some unhappy devs who didn't pick the right tool for the job.

do you read applications from developers at all?

It’s a killer app for technical people that have better things to do than build custom integrations for APIs.

I think most reading this would conclude the article is directed at developers building applications with some kind of user interaction...

I guess I've been reading that documentation from the wrong perspective. I thought they were trying to show me the right way, or at least, a good way, to create apps and add features to them.

I think the feedback was, this looks like a very simple (but possibly useful) app, it should not have such heavy dependencies.

... using a tool designed for the type of app I described. That said, if you want to learn how to use the big complicated tool, it's best to start with a trivial app.

I find it really surprising some people don't use the apps they are developing. If you're not using it day in day out heavily, how can you know what's likely to irritate users.

Use the app all the time, if it's slow or buggy you'll soon get irritated by it enough to fix it :)

As a developer you should be one of the biggest users IMHO


Citation needed.

99% of apps are basic CRUD apps. Aside from a few interactive pages - which you could even write with React - there's zero need for this bloat.

No, your "application" is not Google Docs, Spotify, etc. It's not a SPA.


Depends on what you’re trying to build. It’s pretty useful for generic CRUD apps, which is 90% of business apps when you strip out the marketing speak and design...
next

Legal | privacy