A long time ago I joined a new remote-first company and in my first month they made an event where they brought in all employees from all over the world for a week at a farm hotel for a mix or meetings and leisure activities.
In one specific meeting the CEO was talking app this app that and I was very confused. The product was a server side program that had a web client, an electron app and two native mobile apps. But the CEO was talking about things that didn’t make sense for those apps.
At some point I interrupted the meeting and asked for clarification: what are you talking about when you say app? It’s not the mobile apps?
The CEO made a funny face and mentioned an engineer. I looked at him and he had a smug face and said something along the lines of “well, go on, explain it”. CEO then explained he was talking about the new big project, which was basically an extension system for the server product - and the extensions would be called apps.
That night I found that engineer at the hotel bar and asked more details about it. Turns out he was the team lead on this project and he hated the term “apps” for it and had been very vocal about it before, saying among other things that it would cause confusion with the client apps we have. Most of the company agreed with him at the time but the CEO demanded it be named apps anyway.
These days everyone there thinks that naming it apps was the right call, but I always hated having to refer to them as “server extension app” to avoid any confusion, specially because I often worked on integrations with third party tools and those tools also had their own stuff called apps so instead of just saying something like “the Kabum extension” I had to say “the ChaChin server Kabum app” (as in this example’s context there would also be multiple Kabum clients and ChaChin clients that would all be known as apps too)
A long time ago I joined a new remote-first company and in my first month they made an event where they brought in all employees from all over the world for a week at a farm hotel for a mix or meetings and leisure activities.
In one specific meeting the CEO was talking app this app that and I was very confused. The product was a server side program that had a web client, an electron app and two native mobile apps. But the CEO was talking about things that didn’t make sense for those apps.
At some point I interrupted the meeting and asked for clarification: what are you talking about when you say app? It’s not the mobile apps?
The CEO made a funny face and mentioned an engineer. I looked at him and he had a smug face and said something along the lines of “well, go on, explain it”. CEO then explained he was talking about the new big project, which was basically an extension system for the server product - and the extensions would be called apps.
That night I found that engineer at the hotel bar and asked more details about it. Turns out he was the team lead on this project and he hated the term “apps” for it and had been very vocal about it before, saying among other things that it would cause confusion with the client apps we have. Most of the company agreed with him at the time but the CEO demanded it be named apps anyway.
These days everyone there thinks that naming it apps was the right call, but I always hated having to refer to them as “server extension app” to avoid any confusion, specially because I often worked on integrations with third party tools and those tools also had their own stuff called apps so instead of just saying something like “the Kabum extension” I had to say “the ChaChin server Kabum app” (as in this example’s context there would also be multiple Kabum clients and ChaChin clients that would all be known as apps too)
I would have recommended an extension to interface with a mobile browser extension.
The Mobile Extension App Extension App.