feature: links to other apps

[nick1udwig]

We should be able to put links to other apps like

hd://main:app-store:sys/foo

or

/main:app-store:sys/foo

and have it Just Work

When in an iframe in homepage app should be able to just open that app (if it exists; if not? Prompt to go look in App Store for that app?)

What about in localhost case?

[0x70b1a5]

Dovetails with #805. If we solve this one first, the other one follows. I came to the issues board to raise this problem actually - the appstore frontend would need to talk to the homepage frontend somehow in order to integrate with the iframe js structure nicely anyhow.

It's probably going to end up looking like some kind of navigator:sys process, since processes are all going to have to communicate with the central homepage store to coordinate open, opening, and closing apps, unless I'm mistaken

[nick1udwig]

What are your thoughts on this alternative proposal? @0x70b1a5

prompt

look at hyperdrive/packages/homepage/ui/src and
hyperdrive/packages/homepage/ui/src/components/AndroidHomescreen

applications are served inside of iframes in the homescreen. I want to be able to link from
application to application, opening a new iframe for the appropriate application. Assess if
this is possible purely in the frontend. Don't write code

for more context, applications are served at /process:pacakge:publisher and can serve
endpoints under that such as /process:package:publisher/foo

i want to allow links to /process:package:publisher to open a iframe with that app i.e
using openApp in hyperdrive/packages/homepage/ui/src/stores/navigationStore.ts

is it possible? if so, how would you do it?

claude response

● Based on my analysis of the codebase, yes, it is possible to enable cross-iframe navigation
purely in the frontend. Here's my assessment:

Current Architecture

The homepage serves as a container that loads applications in iframes. Each app is served at
/process:package:publisher with the ability to serve sub-endpoints. The openApp function in
navigationStore.ts:68-194 already handles opening apps in iframes.

How to Implement Cross-App Linking

You can achieve this through postMessage API communication between iframes and the parent
homepage. Here's the approach:

1. Parent Window Message Handler

Add a message listener in the homepage (parent window) that listens for navigation requests
from iframes:

// In AndroidHomescreen component or main app
window.addEventListener('message', (event) => {
  if (event.data.type === 'OPEN_APP') {
    const { process, package_name, publisher, path } = event.data;
    // Use existing openApp function from navigationStore
    openApp({ process, package_name, publisher, path, ... });
  }
});

2. Child iframe Navigation Helper

Applications inside iframes would send messages to the parent:

// In child applications
function navigateToApp(process, packageName, publisher, path) {
  window.parent.postMessage({
    type: 'OPEN_APP',
    process,
    package_name: packageName,
    publisher,
    path: path || `/process:${packageName}:${publisher}`
  }, '*');
}

3. Security Considerations

• Validate message origins to ensure only trusted apps can trigger navigation
• The existing openApp function already handles subdomain security checks (lines 78-163)
• Add origin validation: if (event.origin !== expectedOrigin) return;

4. Integration Points

• The existing AppContainer.tsx component already sets appropriate iframe sandbox
  permissions (line 60)
• The openApp function in navigationStore.ts can be reused without modification
• The app tracking and history management (lines 170-193) will work seamlessly

This approach leverages the existing infrastructure while adding minimal complexity. The
postMessage API is well-supported and allows secure cross-frame communication without
requiring backend changes.

[0x70b1a5]

@nick1udwig Good research. I forgot that iframes can message each other when you control them. I'll get to work on this right away.

[nick1udwig]

done in #840