HiHello VS Ember-cli

• Eco-friendly
  HiHello eliminates the need for physical business cards, reducing paper waste and promoting environmental sustainability.
• Convenience
  Digital business cards can be easily updated and shared, allowing for real-time changes without needing to print new cards.
• Integration
  HiHello integrates well with various platforms and tools, such as CRM systems and email clients, improving business workflow.
• Customizability
  Users can personalize their digital cards with unique designs, photos, videos, and links, making them more engaging.
• Analytics
  The platform provides insights into how, when, and where your digital business cards are viewed and shared, offering valuable metrics.

Possible disadvantages

• Dependency on Technology
  The effectiveness of HiHello relies on the recipient's willingness and ability to use and understand digital business cards.
• Privacy Concerns
  Storing and sharing personal information digitally can raise concerns about data security and privacy.
• Initial Learning Curve
  Users who are accustomed to traditional business cards might need time to adapt to the digital format and features of HiHello.
• Internet Requirement
  To fully utilize HiHello, internet access is often necessary, which can be a limitation in areas with poor connectivity.
• Subscription Costs
  While HiHello offers a free tier, advanced features and extensive customization options may require a paid subscription, which can be a deterrent for some users.

• Convention over Configuration
  Ember-cli enforces strong conventions for file structure, naming, and project organization, which reduces decision fatigue and makes it easier for developers to jump between different Ember projects with minimal onboarding time.
• Built-in Tooling
  Comes with a robust set of built-in tools including a development server, testing framework integration (QUnit), asset compilation, and live reload, reducing the need to manually configure and integrate third-party build tools.
• Addon Ecosystem
  Ember-cli supports a rich ecosystem of addons that can be easily installed and integrated into projects, allowing developers to extend functionality without reinventing the wheel for common features.
• Blueprints and Generators
  Provides powerful generator commands (blueprints) that scaffold components, routes, models, and other application pieces quickly, speeding up development and ensuring consistency across the codebase.
• Stable Long-term Support
  Ember-cli follows Ember's release cycle with clear LTS (Long Term Support) versions, providing stability and predictability for teams maintaining large applications over time.

Possible disadvantages

• Steep Learning Curve
  The strict conventions and unique architecture of Ember-cli can be difficult for newcomers to learn, especially those coming from more flexible frameworks or with no prior Ember experience.
• Smaller Community Compared to Alternatives
  Compared to tools like Vite, Webpack, or CRA used with React/Vue, Ember-cli has a smaller community and ecosystem, which can mean fewer third-party resources, tutorials, and community-driven troubleshooting.
• Build Performance
  For large applications, Ember-cli's build process can become slow, and while improvements have been made with embroider, some developers still report slower build times compared to more modern bundlers.
• Rigid Structure
  The opinionated nature of Ember-cli, while helpful for consistency, can feel restrictive for developers who prefer more flexibility in structuring their applications or adopting non-standard patterns.
• Migration Complexity
  Upgrading between major Ember-cli versions or migrating to newer build systems like Embroider can be complex and time-consuming, particularly for older or heavily customized applications.

See How Hi Hello Works

No Ember-cli videos yet. You could help us improve this page by suggesting one.

Tracking HiHello since Mar 2021.

• Help! Why does chrome console inner text and my program inner text not return the same values? (spent nearly the whole day trying to extract an element). Turned to reddit as its always had the best community. Any help is MASSIVELY appreciated. Puppeteer!!

  The webpage is LinkedIn.com. While this isn’t a framework, I know that are using https://cli.emberjs.com/release/. Source: about 5 years ago