My company produces around 10-20 web projects per year for small companies and web entrepreneurs. Our clients, often business-oriented, are busy chasing investors and winning awards, while we are looking after their Web Software. However interacting with them is very important and we are looking for a better ways to do so.
Since we are developing web-software, why not use that web-software to interact with the client? In this article I am explaining how to go through a steps to develop a simple yet robust feedback system.
It’s been 4 years since I showed up for M50 Enterprise Program (Government program helping start-ups in Ireland) dressed in jeans and t-shirt. I had an idea for on-line project and I wanted to pursue my goal. My belief was that if I write a great software and make it look good, people would certainly start using it. Sometimes it turns out to be like that, but it rather an exception that a rule.
Back then my idea failed, however I have learned two important things about software development:
- Research is very important. Talk with potential clients of what they want before putting your effort into making it.
- Find a shortest path to your goal. Make things work first, then make them work good.
By sticking to those two rules you can avoid spending time on something unnecessary, failing a project or even go bankrupt. Let’s see in more details how to achieve those goals in practice with help of Agile Toolkit.
Agile Toolkit is a new — more efficient way way to build Web Software.
Agile Toolkit is a high-performance PHP framework for UI development with jQuery. High levels of efficiency are achieved because your database and your UI are seamlessly and securely integrated. You achieve more with less code
We are getting ready to unveil our new website for Agile Toolkit. A lot of things are still being written and added, but we decided to share it with readers of this blog.
I would love to hear any feedback on the website or in general.
Get in Touch
We are trying to reserve a spot to talk on Bizcamp Newry. http://www.bizcampnewry.com/. This would be our first public talk / announcement. Please follow us on twitter for more updates: http://twitter.com/atk4
I came over this old question on StackOverflow: “Which PHP Framework will get me to a usable UI the fastest?” I couldn’t help but wonder, why people are not aware of all those other PHP UI frameworks? There are few, right? If you google for “php ui” you can find them. Those are more generally referred to as UI toolkits. But why those toolkits are not known in the mainstream?
Why there is a gap between UI toolkits and mainstream frameworks? If UI is Yin and backend is Yang – why can’t they co-exist?
Here is what I think..
For each project it usually takes some time to set up basic things. We wanted to make it easier for people who are only starting with Agile Toolkit. So we are now including a sample project, which you can “svn export” to get started much faster.
I stumbled upon a interesting jQuery plugin called Validity. Syntax seemed straightforward so I decided to see how long it takes to integrate it into Agile Toolkit.
See demo here: http://demo.atk4.com/validity.html
Up till now we had to either pile up functions in API class formatted as page_user, page_user_add, page_user_del, or we had to create all those classes, each in it’s own file.
Well – not anymore. Now any page class can have sub-pages. Here how it works:
Password complexity is a fine balance between memorable passwords and crack-able passwords. But how you measure that? For instance “john192″ is much easier to crack than “9john2″. However password strength tests approach both with the same algorithm. Even company policies are being made up requiring passwords to cary certain amount of digits or symbols.
A fine line is drawn by a CrackLib – a library coming a long way from Unix and designed for a single purposes of assessing password strength. This article is about how to integrate CrackLib into password verification field.
You can see demo: http://agiletech.ie/pwcheck/