Ember.js

Ember.js PHP MySQL Propel Slim Intercom

Mostly CRUD app, using propel orm, jsonapi serializers and ember.js frontend, this app was in ember 2.16 and we recently upgraded without any issue to 3.15, propel is super good as ORM, slim is a thin framework basically for routing and middleware

Firebase Go Ember.js React Native React GraphQL SendGrid MySQL

Emberjs for our admins panels using ember-apollo and react native using apollo too for our apps, using golang graphql, services like SendGrid to send all the emails, Conekta to for accepting credit cards, firebase for our auth with facebook, google, phone, etc...

Ember.js Algolia Go Google App Engine Firebase MySQL

The new ember.js with SSR using fastboot+prember, without jquery and with npm easy installs via de ember-auto-import addon, angle bracket components in handlebars and ES6 classes is just a breeze to develop, we wanted to try golang for this particular project and it's ok, but I wouldn't recommend it for fast CRUDs, we might change to Elixir Phoenix for the next project, although algolia is super good there are no shortcuts for ember, we had to build them from scratch, but it works super good, we use firebase for our auth with facebook, google, phone, etc...

We recently decided to rewrite Ucraft's Laravel from scratch.

The goal is to make everything more Laravel friendly that will speak to frontend JavaScript , built on Ember.js via JSON Patch standard. This will also make out app better extendible and overridable.

The namespeaces are going to be more correct and the app itself will be compatible with Composer packages.

This also improves the connection between MySQL and PHP making the reoccurring MySQL queries cached during the lifecycle.

One of our favorite "tools" at Hyperlogs is Ember.js and Firebase. They are extremely powerful and productive when combined. Give them a look and stop fighting with your react framework :)

We needed a frontend framework for to make it easier to work with JavaScript. We chose Next.js since it maintains the flexibility of something like Create React App but gives some structure on how to organize the app similar to Ember.js.

Webpack and Babel are configured out of the box for #ServerSideRendering, #TreeShaking, and other nice #JS features.

Shortly after I joined Algolia as a developer advocate, I knew I wanted to establish a place for the community to congregate and share their projects, questions and advice. There are a ton of platforms out there that can be used to host communities, and they tend to fall into two categories - real-time sync (like chat) and async (like forums). Because the community was already large, I felt that a chat platform like Discord or Gitter might be overwhelming and opted for a forum-like solution instead (which would also create content that's searchable from Google).

I looked at paid, closed-source options like AnswerHub and ForumBee and old-school solutions like phpBB and vBulletin, but none seemed to offer the power, flexibility and developer-friendliness of Discourse. Discourse is open source, written in Rails with Ember.js on the front-end. That made me confident I could modify it to meet our exact needs. Discourse's own forum is very active which made me confident I could get help if I needed it.

It took about a month to get Discourse up-and-running and make authentication tied to algolia.com via the SSO plugin. Adding additional plugins for moderation or look-and-feel customization was fairly straightforward, and I even created a plugin to make the forum content searchable with Algolia. To stay on top of answering questions and moderation, we used the Discourse API to publish new messages into our Slack. All-in-all I would say we were happy with Discourse - the only caveat would be that it's very helpful to have technical knowledge as well as Rails knowledge in order to get the most out of it.

Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

We're using a 100% Ember application in our main website, bytelore.com, after we decided to refactor it. Ember.js