wow... This ubports project is really born dead. uninstalling this junk from my phone

Acknowledged Accomplishments

The team has achieved impressive milestones:

• Ubuntu 24.04 LTS upgrade completed (September 2025)
• Waydroid integration shipping by default on Halium 9+ devices
• VoLTE support working on Mediatek devices
• Snap support enabled by default in 24.04
• Personal data encryption implementation
• Theme live-switching capabilities

These represent significant technical accomplishments by a volunteer-driven project.

Core Strategic Concern

The central issue appears to be resource allocation: development effort is invested in areas that may not address the primary barriers to user adoption.

1. Browser Development Challenge

Current situation:

• Morph browser maintained by small team
• No extension support (including ad blocking)
• Ongoing security update requirements
• Complex codebase maintenance burden

Historical context:
Only well-resourced browser projects have remained viable long-term (Firefox with Mozilla, Chromium with Google backing).

Alternative approach:
Consider adopting Firefox Mobile or Chromium-based solution with privacy enhancements, allowing browser development resources to redirect toward core OS improvements.

User impact: Privacy-conscious users expect basic functionality like ad blocking, which is currently unavailable.

2. Custom Packaging Systems

Current approach:

• Click packages (legacy)
• Ubuntu SDK (community-maintained)
• Recently enabled Snap support

Challenge: Maintaining multiple packaging systems with limited resources.

Alternative consideration:
Accelerate transition to established packaging formats (Snap, Flatpak) to tap into broader Linux ecosystem and reduce maintenance overhead.

3. Application Ecosystem Strategy

Current model: Custom applications for core functions (browser, calendar, email, calculator, gallery, music player).

Resource reality: Each custom application requires ongoing development, security updates, and feature parity efforts.

Distribution model comparison:
Major Linux distributions (Debian, Arch, Fedora) focus on packaging existing quality FOSS applications rather than developing custom alternatives.

Suggested approach:

• Package best-in-class existing FOSS applications
• Maintain only mobile-specific components (shell/UI, system settings, core integration)
• Contribute improvements upstream to benefit entire FOSS ecosystem

4. Waydroid Integration Opportunity

Current status: Waydroid ships by default on Halium 9+ devices (positive development).

Improvement opportunity:

• Include in first-boot setup wizard
• Deeper launcher integration for seamless app appearance
• Unified notification system
• Transparent file sharing

Strategic framing: Position as feature rather than workaround - "Run Android apps while maintaining full Linux system" similar to Wine on desktop Linux.

Comparison: PostmarketOS Approach

PostmarketOS demonstrates alternative strategy:

• 500+ device ports versus Ubuntu Touch's approximately 50
• 700+ contributors and growing
• Active funding (NGI grants, reserves over 40k EUR)
• Reuses existing components (Alpine packages, established desktop environments)
• Monthly development updates with community engagement

Key difference: Focus on making Linux work on mobile hardware rather than rebuilding entire application stack.

Migration Barrier Analysis

Significant adoption barrier: No migration tooling exists to help users switch from Android.

Current user experience:

1. Manual backup of Android device
2. Flash Ubuntu Touch
3. Manual restoration of contacts, messages, photos, app data
4. Time-intensive setup process

Comparison: iOS provides "Move to iOS" app for Android to reduce switching friction.

Proposed solution: Ubuntu Touch Migration Assistant

Android-side component (F-Droid app):

• Export contacts (vCard format)
• Backup messages (encrypted)
• Transfer media library
• Export browser data (bookmarks, encrypted passwords)
• Calendar and event export
• System settings (WiFi networks, Bluetooth pairings)
• App inventory for alternative suggestions

Ubuntu Touch-side component:

• First-boot migration wizard
• Automated data restoration
• FOSS alternative suggestions for Android apps
• Waydroid setup for essential applications
• Configuration preservation

Impact: Reduces primary psychological barrier to switching - fear of data loss.

Resource Allocation Suggestion

Current distribution (estimated):

• Browser maintenance: 15%
• Custom applications: 10%
• Multiple packaging systems: 10%
• Shell/UI: 10%
• Core OS (hardware, drivers): 25%
• Waydroid integration: 15%
• Major upgrades: 15%

Suggested focus:

• Hardware support and Linux core: 50%
• Shell/UI and convergence: 20%
• Waydroid integration polish: 15%
• Single packaging system: 10%
• Migration tooling: 5%

Convergence as Differentiation

Unique value proposition: Full desktop Linux environment accessible via phone form factor.

Competitive analysis:

• Samsung DeX: Limited to Android applications
• iPad: Cannot run desktop applications
• Other mobile Linux: Variable convergence quality

Opportunity: Position as "laptop replacement in pocket" with seamless transition between mobile and desktop modes.

Recommended Strategic Shifts

1. Adopt established browser solution (Firefox Mobile or privacy-focused Chromium)
2. Complete transition to single packaging format (Snap or Flatpak)
3. Package existing quality FOSS applications rather than maintaining custom versions
4. Polish Waydroid integration for seamless Android app compatibility
5. Develop migration tooling to reduce switching barriers
6. Focus majority resources on hardware support, power management, and driver development
7. Emphasize convergence capabilities as primary differentiation

Alternative Keyboard Recommendation

For terminal usage and power users, consider packaging Unexpected Keyboard as default option. It provides excellent FOSS keyboard with superior terminal support, aligning with Linux power-user demographic.

User Requirements for Reconsideration

As someone evaluating alternatives, these improvements would warrant returning to Ubuntu Touch:

1. Browser with extension support (or polished Waydroid browser experience)
2. Migration tool preserving Android data during switch
3. Refined convergence capable of laptop replacement
4. Optimized power management for extended battery life

Conclusion

This feedback stems from desire for Ubuntu Touch success rather than criticism. Recent achievements (24.04 upgrade, Waydroid integration, VoLTE support) demonstrate capability for significant technical accomplishments.

The suggestion is ruthless prioritization: focus on unique capabilities (full Linux on mobile hardware, convergence) while leveraging existing FOSS solutions for common problems (browsing, applications, packaging).

Current trajectory shows technical competence but may benefit from strategic refocusing on core differentiation rather than reimplementing solved problems.

The volunteer team has proven ability to execute difficult technical challenges. The question is whether resources can be concentrated on areas providing maximum user value and competitive differentiation.

---

Feedback from Linux enthusiast evaluating mobile alternatives

@Moem
I'm grateful that you noticed my post and took time to have a conversation with me. Thank you for that!

Exactly, it's a handful of devs, and I'm very frustrated to see that so much talent is wasted on maintaining:

Custom software Ubuntu Touch maintains:

• Morph Browser - Custom QtWebEngine browser without extension support (when Firefox Mobile exists with full extension ecosystem)
• Custom core apps: Calculator, Email client, Calendar, Clock, Gallery, Notes, File Manager, Music player, etc. - when mature FOSS alternatives exist (GNOME Calculator, Geary, GNOME Calendar, etc.)
• Click packaging system - alongside Snap support now (maintaining TWO packaging systems)
• Lomiri/Unity 8 shell - entire custom mobile UI/shell
• Ubuntu SDK - custom development toolkit
• Libertine containers - custom solution for desktop apps

Yes, I am impressed that people, the open source community, the UBports community in particular cracked VoLTE among other achievements like the 24.04 upgrade. These are REAL accomplishments.

But at the same time, the OS doesn't even ship a decent resource monitor. htop isn't even available by default, and users have to ask why it's not included. The preinstalled apps are mostly custom "core apps" like calculator, email, and file manager rather than proven system utilities that would help users understand what their OS is doing. Even shipping htop by default would show that devs understand what an OS actually needs.

But again, I see this over and over again in FOSS: people reinvent apps when such FOSS apps already exist, fork whole distros instead of making configuration sets/setup scripts, reinvent damn web browsers... And we all end up with thousands of half-baked apps, OSes, and projects.

Meanwhile, look at what Droidian and Mobian are doing: They use pure Debian packages, desktop Firefox with extensions, existing DEs (Phosh/Plasma Mobile), and focus their limited resources on making Linux work on mobile hardware. They don't waste time rewriting calculators.

And every time I try to draw people's attention to this pattern, everyone acts like it's nothing, like there is clearly no issue at all. But the user numbers tell a different story - Ubuntu Touch isn't growing, while projects that leverage existing FOSS infrastructure (like PostmarketOS with 700+ contributors) ARE growing.

I don't say this to attack - I say it because I genuinely wanted Ubuntu Touch to succeed, and it frustrates me to see talented volunteers burning time on problems that have already been solved by the broader FOSS community.

@Moem I did. No one even replied to my post about a year ago. Clearly the project maintainers to busy padding each others backs for making updated versions of calculator and browser. I dont know how many YEARS this project needs to understand what many other projects learned the hard way - DO NOT REINVENT Fing BROWSERS - its a dead end. And os makers making their own custom browser... instead of at least implementing decent keyboard suited for terminal (that is already exists in FOSS - unexpected keyboard).
I don't know where is it i can help here, when the whole building is on fire and it habitants acting as it is fine, making me a weirdo for pointing obvious flaws.

@uxes less corp fucked up version https:// claude . ai/public/artifacts/e810a24a-00f4-42ea-aed3-24a780428c2f

@uxes anyway fuck ubports. the project is led by snobs and the aggressive spam filter on legitimate posts proves it. TL;DR the project wastes resources reinventing the wheel with custom calculators and browsers while the core OS remains unusable.

@uxes thank to fucking "spam protection" that ubports forum uses. It was complaining about the post over and over again until i put it into claude with max sugarcoting/corptalk setting. What a waste of time for setting up such "spam" /censorship system

Acknowledged Accomplishments

The team has achieved impressive milestones:

• Ubuntu 24.04 LTS upgrade completed (September 2025)
• Waydroid integration shipping by default on Halium 9+ devices
• VoLTE support working on Mediatek devices
• Snap support enabled by default in 24.04
• Personal data encryption implementation
• Theme live-switching capabilities

These represent significant technical accomplishments by a volunteer-driven project.

Core Strategic Concern

The central issue appears to be resource allocation: development effort is invested in areas that may not address the primary barriers to user adoption.

1. Browser Development Challenge

Current situation:

• Morph browser maintained by small team
• No extension support (including ad blocking)
• Ongoing security update requirements
• Complex codebase maintenance burden

Historical context:
Only well-resourced browser projects have remained viable long-term (Firefox with Mozilla, Chromium with Google backing).

Alternative approach:
Consider adopting Firefox Mobile or Chromium-based solution with privacy enhancements, allowing browser development resources to redirect toward core OS improvements.

User impact: Privacy-conscious users expect basic functionality like ad blocking, which is currently unavailable.

2. Custom Packaging Systems

Current approach:

• Click packages (legacy)
• Ubuntu SDK (community-maintained)
• Recently enabled Snap support

Challenge: Maintaining multiple packaging systems with limited resources.

Alternative consideration:
Accelerate transition to established packaging formats (Snap, Flatpak) to tap into broader Linux ecosystem and reduce maintenance overhead.

3. Application Ecosystem Strategy

Current model: Custom applications for core functions (browser, calendar, email, calculator, gallery, music player).

Resource reality: Each custom application requires ongoing development, security updates, and feature parity efforts.

Distribution model comparison:
Major Linux distributions (Debian, Arch, Fedora) focus on packaging existing quality FOSS applications rather than developing custom alternatives.

Suggested approach:

• Package best-in-class existing FOSS applications
• Maintain only mobile-specific components (shell/UI, system settings, core integration)
• Contribute improvements upstream to benefit entire FOSS ecosystem

4. Waydroid Integration Opportunity

Current status: Waydroid ships by default on Halium 9+ devices (positive development).

Improvement opportunity:

• Include in first-boot setup wizard
• Deeper launcher integration for seamless app appearance
• Unified notification system
• Transparent file sharing

Strategic framing: Position as feature rather than workaround - "Run Android apps while maintaining full Linux system" similar to Wine on desktop Linux.

Comparison: PostmarketOS Approach

PostmarketOS demonstrates alternative strategy:

• 500+ device ports versus Ubuntu Touch's approximately 50
• 700+ contributors and growing
• Active funding (NGI grants, reserves over 40k EUR)
• Reuses existing components (Alpine packages, established desktop environments)
• Monthly development updates with community engagement

Key difference: Focus on making Linux work on mobile hardware rather than rebuilding entire application stack.

Migration Barrier Analysis

Significant adoption barrier: No migration tooling exists to help users switch from Android.

Current user experience:

1. Manual backup of Android device
2. Flash Ubuntu Touch
3. Manual restoration of contacts, messages, photos, app data
4. Time-intensive setup process

Comparison: iOS provides "Move to iOS" app for Android to reduce switching friction.

Proposed solution: Ubuntu Touch Migration Assistant

Android-side component (F-Droid app):

• Export contacts (vCard format)
• Backup messages (encrypted)
• Transfer media library
• Export browser data (bookmarks, encrypted passwords)
• Calendar and event export
• System settings (WiFi networks, Bluetooth pairings)
• App inventory for alternative suggestions

Ubuntu Touch-side component:

• First-boot migration wizard
• Automated data restoration
• FOSS alternative suggestions for Android apps
• Waydroid setup for essential applications
• Configuration preservation

Impact: Reduces primary psychological barrier to switching - fear of data loss.

Resource Allocation Suggestion

Current distribution (estimated):

• Browser maintenance: 15%
• Custom applications: 10%
• Multiple packaging systems: 10%
• Shell/UI: 10%
• Core OS (hardware, drivers): 25%
• Waydroid integration: 15%
• Major upgrades: 15%

Suggested focus:

• Hardware support and Linux core: 50%
• Shell/UI and convergence: 20%
• Waydroid integration polish: 15%
• Single packaging system: 10%
• Migration tooling: 5%

Convergence as Differentiation

Unique value proposition: Full desktop Linux environment accessible via phone form factor.

Competitive analysis:

• Samsung DeX: Limited to Android applications
• iPad: Cannot run desktop applications
• Other mobile Linux: Variable convergence quality

Opportunity: Position as "laptop replacement in pocket" with seamless transition between mobile and desktop modes.

Recommended Strategic Shifts

1. Adopt established browser solution (Firefox Mobile or privacy-focused Chromium)
2. Complete transition to single packaging format (Snap or Flatpak)
3. Package existing quality FOSS applications rather than maintaining custom versions
4. Polish Waydroid integration for seamless Android app compatibility
5. Develop migration tooling to reduce switching barriers
6. Focus majority resources on hardware support, power management, and driver development
7. Emphasize convergence capabilities as primary differentiation

Alternative Keyboard Recommendation

For terminal usage and power users, consider packaging Unexpected Keyboard as default option. It provides excellent FOSS keyboard with superior terminal support, aligning with Linux power-user demographic.

User Requirements for Reconsideration

As someone evaluating alternatives, these improvements would warrant returning to Ubuntu Touch:

1. Browser with extension support (or polished Waydroid browser experience)
2. Migration tool preserving Android data during switch
3. Refined convergence capable of laptop replacement
4. Optimized power management for extended battery life

Conclusion

This feedback stems from desire for Ubuntu Touch success rather than criticism. Recent achievements (24.04 upgrade, Waydroid integration, VoLTE support) demonstrate capability for significant technical accomplishments.

The suggestion is ruthless prioritization: focus on unique capabilities (full Linux on mobile hardware, convergence) while leveraging existing FOSS solutions for common problems (browsing, applications, packaging).

Current trajectory shows technical competence but may benefit from strategic refocusing on core differentiation rather than reimplementing solved problems.

The volunteer team has proven ability to execute difficult technical challenges. The question is whether resources can be concentrated on areas providing maximum user value and competitive differentiation.

---

Feedback from Linux enthusiast evaluating mobile alternatives

wow... This ubports project is really born dead. uninstalling this junk from my phone

postmarketos has a great bootstrap script, to get started, to not bloat main system, to automate rutine processes, guide on the porting process, etc.

Does anyone interested in adopting the script, or making own script for ubports bootstrap ? With text based gui and stuff

https://gitlab.com/postmarketOS/pmbootstrap