One of our recent projects was all about “reaching goals”. Users reaching goals make important decisions and step-by-step move toward the “grand summit” – their purpose – and this web app that our team worked on tracks and manages this progress.
For one of my recent projects I implemented transitions between screens in a web app so they looked and behaved exactly like they do natively on iPhone. Since the task was quite interesting, today I'm sharing my solution here.
Recently we investigated how to create transparent Activities for Android and today we continue the topic of mobile app UI design – but this time with iOS.
Usually developing a tablet version of an existing mobile app that’s been optimized for a smartphone is fast and easy: you can use Fragment, decompose Entities, etc. However, the task within one of our recent projects was rather unique: we were not only making a tablet version for an application based on the ActionBarSherlock library but we also needed first, to implement a Floating Activity, i.e., a transparent Activity so that users could input the required information while also being able to see other Activities or the app itself on the screen in the background; second, to preserve the original size of the floating activity in both portrait and landscape orientations of the device.
Today’s post focuses on how to use RabbitMQ in Symfony2-based projects. RabbitMQ is an open-source messaging broker: it accepts, stores, and forwards messages — in binary blocks of data.
While working on a recent project — a business automation system for an insurance company with one function that allowed for sending important, confidential e-mails to a select number of users simultaneously — our Azoft development team encountered a problem: The mail server with which our app worked couldn’t verify if an email recipient’s account was active. Since it is crucial for the company to know whether certain individuals have received an email or not, we enhanced the system to be able to process undelivered email and generate automatic sender notifications that include all necessary information (incorrect email address, specific error returned, etc.).
There are a number of solutions to this task that work properly only in modern browsers supporting CSS animation, which renders useless certain versions of IE. However, there are still users of outdated versions of IE and — for those who may benefit — today's post includes a script providing backwards-compatible browser animation. CSS3 will be used for Firefox, Chrome, and Safari; jQuery gets the call for use in IE7.