DotNetOpenAuth VS React-Ionic

• Comprehensive Support
  DotNetOpenAuth supports multiple OAuth and OpenID versions, making it versatile for different authentication scenarios.
• Security Features
  The library includes built-in features to handle security concerns, such as token encryption and secure transmission protocols.
• Community and Documentation
  DotNetOpenAuth has a history of strong community support and extensive documentation, which can be helpful in learning and troubleshooting.
• Integration with .NET Framework
  The library is designed to integrate seamlessly with the .NET framework, making it easy to implement in existing .NET applications.

Possible disadvantages

• Complexity and Learning Curve
  The library offers many features, which can make it complex and difficult to learn for newcomers.
• Maintenance and Updates
  There have been concerns about the frequency of updates and maintenance, which might affect long-term usability and compatibility with new standards.
• Limited .NET Core Support
  DotNetOpenAuth primarily targets the .NET Framework, with limited support for .NET Core, which may necessitate alternatives for modern applications.
• Performance Overhead
  The extensive feature set can introduce performance overhead, particularly in scenarios that require lightweight solutions.

• Cross-Platform Development
  React-Ionic allows developers to build applications that run on both iOS and Android platforms using a single codebase, effectively saving time and resources.
• React Ecosystem
  Integration with the React ecosystem provides access to numerous libraries and tools, allowing developers to use familiar technologies and streamline the development process.
• Ionic Components
  Leverages Ionic's UI components that are designed to look and feel native on both iOS and Android, providing a consistent and polished user experience across platforms.
• Live Reloading
  Features like live reloading and hot module replacement can speed up the development process by allowing developers to see changes in real-time.
• Community Support
  Being part of the larger React and Ionic communities, developers can tap into extensive community support and resources to help solve issues and improve their applications.

Possible disadvantages

• Performance Overhead
  Applications built with React-Ionic may experience performance overhead compared to fully native apps, which can be a concern for performance-intensive applications.
• Learning Curve
  Developers new to the ecosystem might face a learning curve due to the combination of React and Ionic concepts and components.
• Platform-Specific Customization
  While React-Ionic provides cross-platform functionality, achieving platform-specific look and feel or leveraging native features can require additional customization and work.
• Ecosystem Dependence
  Reliance on both the Ionic framework and React means developers must stay current with updates and changes in both ecosystems, which can cause maintenance challenges.
• Bundle Size
  The inclusion of both React and Ionic libraries can lead to larger application bundle sizes, which might impact load times and performance on lower-end devices.

• OpenID Provider open source library

  But if the OpenID server would be for a intranet or low number of requests, you can go ahread (in my opinion) and the post also recommends http://dotnetopenauth.net/ because has a OpenID provider and samples. Source: about 4 years ago

Tracking React-Ionic since Mar 2021.