Hacker News new | past | comments | ask | show | jobs | submit login

Ah yes. Because an app optimized for touch on a tiny screen will scale beautifully to work with precise controls via keyboard and mouse/trackpad on large and huge screens.

As evidenced by all the professional apps that require little to no modifications.

Oh wait...




Yes, like the examples I gave.

It sounds like you’re imagining Photoshop in a mobile form factor, which is way besides the point.


> Yes, like the examples I gave.

Small primitive apps with little functionality and barely anything beyond text. Or really limited in their functionality. Or have to hide the absolute vast majority of their interface behind multiple clicks.

Also. Telegram isn't "smartphone-style". It's a native app.

> It sounds like you’re imagining Photoshop in a mobile form factor

Yes, I am. Because here's the list of apps I actually use daily:

- IntelliJ IDEA

- Figma/Sketch

- GitUp

- Terminal/iTerm

Oh, look. All of them cannot be "it's just mobile apps, just blow them up, they will work with little to no midification"


You’re talking about turning desktop apps into phone apps. I’m talking about turning phone apps into desktop apps. The former is hard, the latter is easy.

> Telegram isn't "smartphone-style". It's a native app.

With 95-100% (depending on usage) smartphone UX. If the iOS apps on M1 macs situation wasn’t such a fiasco I’d like to compare the two. My prediction: Loss of keyboard features, drag & drop, not much else (GAIN of image editing).

> Or have to hide the absolute vast majority of their interface behind multiple clicks.

It’s arguable whether this is a good thing or not, but that’s exactly where desktop software is going, likely to reduce clutter. It’s not a necessity for a convergent approach to work, however. Of course you can expand menus and such depending on your platform (one might say in a “responsive” fashion).

Seems like the web of 2012 all over again.


> You’re talking about turning desktop apps into phone apps.

I'm talking about the expectations of a desktop app.

> The former is hard, the latter is easy.

It definitely isn't easy.

There's no easy way to transform an app optimised for imprecise touch on small screens into an app requiring precision inputs on a large screen.

There's no easy way to transform an app optimised to display information on a small screen into an app optimised to display information on a large screen.

> With 95-100% (depending on usage) smartphone UX.

It doesn't matter how much usage it gets on the phone. Telegram app on Mac OS is a native app (it's a native app on Windows, too).

> If the iOS apps on M1 macs situation wasn’t such a fiasco

You can't even comprehend why it's a fiasco.

> It’s arguable whether this is a good thing or not, but that’s exactly where desktop software is going, likely to reduce clutter.

It's not "reducing clutter". It's people who spend most of their lives on the phone not understanding how desktop software works and its requirements. You are a prime example of one such person.

> Of course you can expand menus and such depending on your platform

There's no easy way to "just expand the menus". Then you either get a bad experience on the small screen or a bad experience on the big screen, because requirements are completely different.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: