Another sale for RDPMaster today ๐
One more Mac user now connects to RDP, SSH and VNC from one native app.
Thank you for the trust. Launch on MacPip is on Nov 27.
I can't believe it. First sale! ๐
RDPMaster made its first sale just 4 days after launch.
Thank you to everyone who tried it and shared it. This is only the start. ๐
#buildinpublic#indiehackers#macOS
I made a Jira skill for Claude Code ๐
Tell your agent 'check PROJ-123' or 'are my In Review cards done?'. It reads the issue, checks it against the code, and does the work.
npx skills add https://t.co/4yHbZuflVv --skill jira
Build an MVP. Then test product-market fit.โจThat era is over.
AI builds a full product in days. Code is not the bottleneck now.
The new question is not can we build it?โจIt is who will pay, and how do we reach them?
Distribution wins. Not code
@Elegying1993@macpiphq Thanks! All connections live in one sidebar. You can group hosts into folders, add tags and find any host with quick search. SSH, RDP and VNC sit side by side, so you don't need 3 apps.
Smithdeck ๐ Smithdeck is a native macOS app for Laravel Forge.
It launches on @macpiphq, the free Mac app directory, on Nov 23: https://t.co/X1FpHofU3Z
Cumba ๐ A native Mac window manager: snap windows to halves.
It launches on @macpiphq, the free Mac app directory, on Nov 27: https://t.co/WaHpcjDNdD
We're launching RDPMaster on Dec 14 on ProductsFarm, a weekly launch board for new products.
What it does: Native Mac client for RDP, SSH and VNC connections.
Save the link: an upvote that week would mean a lot.
https://t.co/0VXnEs65ot
I am not saying UX is dead. But AX is next.
We used the first computers by hand.
Switches, cables, punch cards.
Then came the keyboard and mouse. Then phones with keys.
Then Apple removed the keyboard from the phone, and Steve Jobs said our fingers were enough. The MacBook trackpad got so good that we forgot about the external mouse.
Look closely. Each step did the same thing: it removed one more layer between people and machines.
Now it is the keyboard and mouse's turn.
We say what we want, and an agent does the work. No menus, no forms, no clicking through ten screens. Soon we will not even type. We will just talk.
The software side is even more interesting. Our sites and dashboards are not only for people now. Agents use them too. An agent does not care about button colors.
Animations do not impress it. It asks one question: can I do this job fast and without errors?
The agent's interface is not a screen. It is the API and MCP.
APIs have existed for years, but most products treated them as an afterthought. Teams built the dashboard first and added the API later. Now that order is flipping. If a product has a weak API or bad docs, an agent cannot use it.
MCP (Model Context Protocol) goes one step further. Your product tells the agent: "Here are my tools. Here is what you can do." The agent connects and does the work, with no custom integration. It is like a USB port for agents.
For years we asked: can the user find this button? Now the question is: can the agent finish this job in one go?
I call this AX: Agentic Experience.
Interfaces will not disappear. But we will no longer be the first users of our own products.