Platform Notes

The Second Life viewer does not support full external audio handling for HUD-based apps.

• Calls in-world function as signals only (ring, accept, decline, missed call).
• No true live voice audio inside the HUD.

• Real voice calling is available when both users use the web version with microphone access.
• Inside Second Life, calls remain limited to signaling behavior.

The embedded browser in the Second Life viewer does not reliably store or maintain cookies and sessions.

• Users may need to log in repeatedly to external apps.
• Sessions may reset between uses.
• External apps can behave differently than in a normal browser.

• ONEPHONE reduces dependence on external websites where possible.
• For third-party or embedded web services, repeated sign-in may still be unavoidable inside the viewer.

Media-on-a-Prim and the built-in viewer browser are more limited than modern web browsers.

• Some apps may not scale or respond properly.
• Certain platforms may feel slower or partially unsupported.
• Not all web features behave as expected.

• Apps are optimized where possible for in-world use.
• Some services will still work better in a normal external browser than inside the viewer.

Second Life does not reliably provide access to full-resolution textures via UUID.

• Only preview or thumbnail images are accessible externally.
• Images may appear cropped, compressed, or distorted.
• Original aspect ratios are not guaranteed.

• UUID-based image importing is limited or disabled where quality cannot be guaranteed.
• Recommended workflow: save images locally from Second Life and upload them directly to ONEPHONE.

Second Life does not offer an API for uploading textures from external systems.

• Images cannot be sent from ONEPHONE or the web directly into Second Life inventory.
• All uploads must go through the viewer manually.
• Upload fees are controlled by Second Life.

• ONEPHONE can manage images within its own system (gallery, albums, sharing).
• Manual upload through the SL viewer remains required for bringing images into Second Life.

The in-world environment is not a full mobile operating system or modern browser.

• Some interactions differ from real smartphones.
• Certain websites or features may behave inconsistently.
• Not all mobile-like functionality can be replicated.

• ONEPHONE is designed to feel as close as possible to a smartphone within these limits.
• Some browser-related differences remain unavoidable inside the viewer.

Second Life does not expose real device hardware such as camera, microphone, storage, or native notifications to HUDs.

• No native camera integration.
• Limited microphone and audio handling.
• No true push notification system like on iOS or Android.

• Hardware-dependent features are only supported where the environment allows it.
• In-world HUD functionality remains limited by what the viewer exposes.

HUDs operate within fixed viewer constraints and can vary across screen sizes and UI scales.

• Text and UI elements may appear too small on certain screens.
• Layout flexibility is more limited than on websites or real mobile apps.

• UI scaling and layout improvements are added where possible (including adjustable text size).
• The interface continues to be refined based on user feedback.

Second Life does not support true background processes like a mobile operating system.

• No persistent app-style background execution.
• Features cannot rely on continuous local processing inside the HUD.

• ONEPHONE uses server-driven systems and real-time updates where possible.
• This improves timing and responsiveness, but does not turn the viewer into a full mobile OS.

Second Life scripts have memory, execution, and region performance constraints.

• Complex logic must be managed carefully.
• Performance can vary depending on region load and viewer conditions.

• Heavy processing is moved outside the HUD where possible.
• Systems are optimized to keep the in-world experience as smooth as possible.

Some web behavior is ultimately controlled by the Second Life viewer and not by ONEPHONE.

• Differences in rendering and behavior between users.
• Embedded content may not behave consistently in every case.

• ONEPHONE is built to work as reliably as possible within these limits.
• Some viewer-level behavior remains outside of our control.