11–20 of 83 posts
A lot of medical applications (signal processing, visualization, robot control) tend to be traditional desktop applications.
Also military applications for analysis, and planning are often desktop based because they can not use consumer mobile devices nor can they rely on the "cloud".
Evernote? https://www.crunchbase.com/organization/evernote
not counts. sorry evernote, I loved you though.
Actually most are making native mobile apps. I'm a mobile guy making a cross compatible web app. Why anyone would make a native app in our world of ECMAScript6 and HTML5 is beyond me.
i.e. [citation needed]
Also, the reasons people make native mobile apps rather than hybrid apps (which run inside a mobile web-player component) are speed and reliability. Famously, Facebook switched from HTML5 to native for their iOS app:
https://www.facebook.com/notes/facebook-engineering/under-th...
Mac desktop app (native Cocoa + OpenGL, no web views).
Desktop is pretty much necessary for this tool because it needs to integrate with Xcode and Android Studio.
I can think of Dropbox, Slack, GitHub right now.
Because latency is an absolute premium for playing music in real-time across the internet, we've focused first on the desktop, where we have the most control ... but still find a ton of challenges.
If you saw this recent article about Android and audio latency, you can see why there are challenges in the mobile space: https://news.ycombinator.com/item?id=9386994
If you were to try and build a web-only version of JamKazam, WebRTC is your best bet but it does not have low enough latency, either.
https://www.crunchbase.com/organization/Dropshare