51–60 of 107 posts
The place where they really could have won is iOS, where browsers aren't allowed to use their own rendering engine, and system specs still lagged behind the M1.
I wish Mighty had succeeded for a different audience. The core value prop "make figma faster" was not very compelling--people who need to use Figma can buy a mac. You know who does struggle with slow computers and memory issues? Call center employees who have to run Front, Slack, Chrome, and probably one or two other electron-based apps. At our startup (not in USA), these issues are so bad we've ended up getting peop…
I wish Mighty had succeeded for a different audience. The core value prop "make figma faster" was not very compelling--people who need to use Figma can buy a mac. You know who does struggle with slow computers and memory issues? Call center employees who have to run Front, Slack, Chrome, and probably one or two other electron-based apps. At our startup (not in USA), these issues are so bad we've ended up getting peop…
I always found the idea to be bizarre. The group of people for which a browser is truly horrendously slow would be on something like a low-end Windows laptop. From mid-end and upwards it's fine (or good enough) and for Mac users pretty much never an issue. The people with such crappy hardware are exactly the group to not be able to afford 35$ a month. That's like the price of 3 or 4 streaming services combined. Just…
I had a similar impression of it, the best I can come up with is I think it was a bet based on a prediction of the future that is kinda true, but just doesn't matter as much as they thought. 1. Personal computers are dead and just a means to access a browser via dumb terminals 2. Applications will be Figma style - web based entirely. 3. Intel/AMD chips are bad and not getting that much better (this one is true, but m…
Define "bad". I'm on a 2019 MB Pro with an i9 with 32G of ram. I pretty much never have browser performance issues that bother me. I have Chrome open with 2 windows and a total of 39 tabs, plus some other apps that people always like to bitch about resource-wise (Slack, VSCode). Granted I'm not a designer so I don't have what would be some of the most resource-hungry apps like Figma, but if there is one group of people who I've always seen spend a shitload on their desktops/laptops it's designers.
I think Mighty was always a weird project that pretty much only solved a problem for people that would never be willing to pay for it.
I wish Mighty had succeeded for a different audience. The core value prop "make figma faster" was not very compelling--people who need to use Figma can buy a mac. You know who does struggle with slow computers and memory issues? Call center employees who have to run Front, Slack, Chrome, and probably one or two other electron-based apps. At our startup (not in USA), these issues are so bad we've ended up getting peop…
I always found the idea to be bizarre. The group of people for which a browser is truly horrendously slow would be on something like a low-end Windows laptop. From mid-end and upwards it's fine (or good enough) and for Mac users pretty much never an issue. The people with such crappy hardware are exactly the group to not be able to afford 35$ a month. That's like the price of 3 or 4 streaming services combined. Just…
I had a similar impression of it, the best I can come up with is I think it was a bet based on a prediction of the future that is kinda true, but just doesn't matter as much as they thought. 1. Personal computers are dead and just a means to access a browser via dumb terminals 2. Applications will be Figma style - web based entirely. 3. Intel/AMD chips are bad and not getting that much better (this one is true, but m…
I wish Mighty had succeeded for a different audience. The core value prop "make figma faster" was not very compelling--people who need to use Figma can buy a mac. You know who does struggle with slow computers and memory issues? Call center employees who have to run Front, Slack, Chrome, and probably one or two other electron-based apps. At our startup (not in USA), these issues are so bad we've ended up getting peop…
I wish Mighty had succeeded for a different audience. The core value prop "make figma faster" was not very compelling--people who need to use Figma can buy a mac. You know who does struggle with slow computers and memory issues? Call center employees who have to run Front, Slack, Chrome, and probably one or two other electron-based apps. At our startup (not in USA), these issues are so bad we've ended up getting peop…
I'm surprised they didn't try to pivot to another initial market en route to building a general cloud PC.
My company (https://softdrive.co) is in the same space - our initial focus is on empowering companies running high end graphical workloads (BIM, CAD, etc) using cloud PCs.
Curious why per minute billing appeals to you. Usually we've heard preference for predictable monthly pricing.