Last Updated: 3/10/15
Salva O'Renick believes in the right tool for the right job. Here is an example of a mixture of languages we can deploy depend on the needs and scope of a project:
For desktop browsers, we support and test compatibility for the following browsers:
- Internet Explorer v10 and above
- Chrome – v40 and above
- Firefox – v35 and above
- Safari – v7 and above
If support for legacy version of browsers is required, the specific browsers will need to be requested and a new scope will be created to reflect the change in scope of development.
Tablet Sizes and orientation:
Salva O'Renick supports responsive optimization for mobile devices for both portrait and landscape in the following mobile device sizes:
- 4" smartphone
- 5.5" smartphone
- 7" tablets
- 8" tablets
- 10" tablets
Development, testing, and optimization will be done for WebKit based mobile browsers found in the following operating systems:
- Apple iOS v8 and above
- Google Android v4.4 (Kit Kat) and above
Note: If scope of work dictates icons to be designed and implemented, scope will reflect retina dislpay optimization for icons.
Salva O'Renick uses the Yeoman workflow for the front end coding of projects. This workflow consists of:
While the incorporation of these tools is not a determining factor for end user compatibility, if a client will be hosting the project, these dependencies will need to be taken into consideration in order to further maintain the codebase.
Front End frameworks
Often the scope of work will call for a front end framework to be deployed, either for the prototyping phase of a project or it's end deliverable. Salva O'Renick works with popular front end frameworks:
- Twitter Bootstrap v3 and above
- Foundation v5 and above
- Materialize v0.95 and above
This section is a reference from the server offering article on devdocs
Types of servers
We like Linux Ubuntu cloud based servers with native MySQL databases. The specs of a server will vary based on project needs. If the scale of a project requires or would benefit from an isolated database instance, this can also be executed. The recommendation would be to keep the database in the same account as the server or utilize a cloud based database such as Parse if appropriate.
Salva O'Renick prefers Rackspace, Media Temple, Digital Ocean, and Amazon Web Services as hosting providers. There are many pros and cons to all providers and the selection is made based upon the requirements of the project.
We recommend setting up a server for developing on and a live server that the public sees. We call these stage (development) and production (live). During the intitial web build, stage and production are spun up at the same time. Development is done on stage and will be pushed to production for client review. Once the requirements of the project are met, the domain name will be pointed at the production server and can be publicized to the world. Stage becomes the server for new web functionality and features, bug troubleshooting, and content review. Stage will always maintain a no-index-no-follow code so that search engines do not index its content.
For content sites and web apps that will contain a large amount of assets, we also recommend the presence of a Content Delivery Network (CDN). Amazon S3 is our preferred provider of choice.
The benefit of this infrastructure model is it helps minimize risk or dependency on the server. If a server goes down, it is easier to take a back up, apply it to a new server and then point the CDN at the new server--all files are not lost.
We use Github as a central repository for hosting code and version control.