61–70 of 96 posts
Earlier quoted context omitted.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
Slack should at least bridge to an open protocol, if not use one outright, so I can use any client I want. Like they used to.
Then it became just another crappy messaging app.
Centrally controlled, heavy and bloated - nope, nope, it's just not it.
Time for self-hosted https://rocket.chat :)
Earlier quoted context omitted.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
I can't work out why you wouldn't develop a native app anyway - all this scaffolding in a Web UI to imitate native controls (like menus) seems completely backwards to me. Seems just lazy, but in an odd way because writing native apps isn't rocket science or difficult. It's not like they're implementing thousands of native controls or user interface components - a listview with an edit box at the bottom...
Earlier quoted context omitted.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
Slack should at least bridge to an open protocol, if not use one outright, so I can use any client I want. Like they used to.
Earlier quoted context omitted.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
I can't work out why you wouldn't develop a native app anyway - all this scaffolding in a Web UI to imitate native controls (like menus) seems completely backwards to me. Seems just lazy, but in an odd way because writing native apps isn't rocket science or difficult. It's not like they're implementing thousands of native controls or user interface components - a listview with an edit box at the bottom...
Really? One code base, one language, write features once. I think it's more about eng resourcing (headcount, onboarding, roadmap parity / feature drift, etc) than whether making a native app is hard.
Anecdotal, but I feel like the React Natives and Electrons have made it so you see less "Sorry we're only on Mac", and "We're only on Android, iOS coming soon!" from apps
Earlier quoted context omitted.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
I can't work out why you wouldn't develop a native app anyway - all this scaffolding in a Web UI to imitate native controls (like menus) seems completely backwards to me. Seems just lazy, but in an odd way because writing native apps isn't rocket science or difficult. It's not like they're implementing thousands of native controls or user interface components - a listview with an edit box at the bottom...
Slack is not a good enough replacement for IRC. Centrally controlled, heavy and bloated - nope, nope, it's just not it.
They just added voice calls via web UI. Not E2EE yet but if you're on an encrypted VPN then that's kinda moot anyway.
Earlier quoted context omitted.
Slack should develop native apps now as they are no longer a lean startup and can afford to build native apps.
I can't work out why you wouldn't develop a native app anyway - all this scaffolding in a Web UI to imitate native controls (like menus) seems completely backwards to me. Seems just lazy, but in an odd way because writing native apps isn't rocket science or difficult. It's not like they're implementing thousands of native controls or user interface components - a listview with an edit box at the bottom...