API Integration

[SoftwareToolman]

Hi, Thomas:

I have what I believe is a great software enhancement request.

How about adding the ability to easily integrate the applications we build with exiting APIs/SDKs? For example, integrating with Google or Yahoo Maps, or Amazon Web Services.

This would allow us to build some killer applications that would be highly marketable. Take a look at the site: programmableweb.com and you'll see the thousands of applications/mashups that people are building and promoting using the APIs/SDKs of other companies. By coupling this capability with the built-in database management capabilities in the Tiger Software package, the sky would be the limit.

An additional benefit is that, when you create software using certain companies' APIs, they will list you for FREE on their software directories!! This can bring us literally thousands of potential paying customers without costing us a dime.

You could use examples from mashup software packages as a guide for implementing this, such as kapow.com, rssbus.com, serenasoftware.com, etc.

I already have some great ideas for a particular vertical market I want to attack and I would be happy to work with others to design some killer applications and share in the revenue.

What do you think?

Neil Aronson
The SoftwareToolman

[LorenW]

I'm intrigued by this idea as well. It seems to me that if TSB could pull data from
online tools via the API and then that data could stored and managed on the
desktop in TSB that would open up a lot of possibilities.

[SoftwareToolman]

I'm intrigued by this idea as well. It seems to me that if TSB could pull data from
online tools via the API and then that data could stored and managed on the
desktop in TSB that would open up a lot of possibilities.

Exactly right, Loren. This has possibilities for both vertical and horizontal markets. For example, you can create great new sales tools for a sales force using existing CRM (customer relationship management) APIs, then tie it together with the Google Maps API to help them track potential customers, etc. and store and manage the data in TSB databases. That's a simple example. Once you realize the depth and breadth of available company APIs and web services, it will blow your mind at what would be possible with TSB.

Neil Aronson
The Software Toolman

[TrafficBos]

Hello Neil,

I am truly a software novice, but I had been thinking along the same line as this. You and Loren are on to something. Great post, I think it definitely got some wheels spinning.

Changa G.

[SoftwareToolman]

Hello Neil,

I am truly a software novice, but I had been thinking along the same line as this. You and Loren are on to something. Great post, I think it definitely got some wheels spinning.

Changa G.

Hi, Changa:

Thanks for your comment. I've been in the software industry in one way or another for over 30 years. I haven't seen anything before like what's going on right now. Enterprise users used to constantly complain about the huge backlog of application development requests that the IT departments would be sitting on for months. They got so disgusted that often they would look for ways to bypass IT entirely to get some of their important requests done by others.

Today, with mashup software platforms, they can slam together reports, charts and other applications using company APIs and take care of their needs in a more timely manner. But, naturally the little guy/gal who's running a business is still left in the cold. He's not going to spend the time learning about new-fangled software and stay on top of APIs (probably won't even be aware of what's available) in order to design, create and manage his own set of applications. If he can't buy it at the computer store or online as a complete and usable application he probably won't have anything to do with it.

This gives us a great opportunity. With a super development tool like TSB enhanced with the capability of integrating APIs, we can create and selll these applications to anyone who wants it. We can create whole sets of applications for a niche market and add on a never ending collection of revenue streams. The possibilities are mind boggling.

Neil Aronson
The SoftwareToolman

[DominicW]

As a wishlist item, I think this should be more specific. You mention Google API, that is a great one. API's by nature are language specific and don't always play nice with one another.

To add to your idea of Google, to integrate with major names like the Salesforce API or even ZOHO would be pretty huge steps as well.

Great idea here, I give it a +1 vote


Disclaimer: Yes, I know, not all APIs are language specific... but many are. :) Web APIs that are evolving from SOAP into more mashup style APIs are the best and easiest target I think...

[TigerSoftware]

Great idea and something I will look into this year.

Everyone should start listing what api's they would like to see. The salesforce api would be simply awesome as an addition.


Thomas

[SoftwareToolman]

Hi, Dominic:

Your point is well taken. We should probably focus on the top companies' APIs first like Amazon's AWS, Google, MSN, eBay, etc.

One simple solution one company uses for their mashup infrastructure is to convert everything to an RSS feed. Check out the site at http://www.rssbus.com and look at their software specification. It's clean and elegant and we could probably adapt some of their ideas to TSB. But, I agree with you, we need to keep this simple especially as standards are constantly evolving.

Neil Aronson
The SoftwareToolman

[SoftwareToolman]

Great idea and something I will look into this year.

Everyone should start listing what api's they would like to see. The salesforce api would be simply awesome as an addition.


Thomas

Thanks, Thomas. That's great news!!

I think this will add a whole new dimension to the TSB Software.

For ideas on applications that are already being built using these APIs and to put together a list of top APIs for the first implementation in TSB, I suggest a close review of the site: http://www.programmableweb.com.

As of last count, they show 1,397 APIs available. You can sort them in various ways including by category, so it shouldn't be difficult to put together a reasonable list in short order.

Neil Aronson
The SoftwareToolman

[DominicW]

Hi, Dominic:

Your point is well taken. We should probably focus on the top companies' APIs first like Amazon's AWS, Google, MSN, eBay, etc.

One simple solution one company uses for their mashup infrastructure is to convert everything to an RSS feed. Check out the site at http://www.rssbus.com and look at their software specification. It's clean and elegant and we could probably adapt some of their ideas to TSB. But, I agree with you, we need to keep this simple especially as standards are constantly evolving.

Neil Aronson
The SoftwareToolman

Great info. The RSS feed or XML feeds are read only and would work wonders on sites where there is high profitability through affiliate programs. The ones you listed are top notch and should be targets. EBAY and Amazon do provide API access for their affiliate programs so again, +1 :D

Salesforce and ZOHO could be read only but the true value would be in 2 way communication. I think (don't quote me!) that Salesforce uses an object query language which may not be all that different from the standard that most database software uses as is. (structured vs object... not sure)

I am with Neil though, start with the basics (and the ones that have profit potential) - Amazon, Ebay. Google too, because it provides high value added features to the contact and company modules or custom modules that deal with locations.

Top notch idea if it can be implemented.

[SoftwareToolman]

Great info. The RSS feed or XML feeds are read only and would work wonders on sites where there is high profitability through affiliate programs. The ones you listed are top notch and should be targets. EBAY and Amazon do provide API access for their affiliate programs so again, +1 :D

Salesforce and ZOHO could be read only but the true value would be in 2 way communication. I think (don't quote me!) that Salesforce uses an object query language which may not be all that different from the standard that most database software uses as is. (structured vs object... not sure)

I am with Neil though, start with the basics (and the ones that have profit potential) - Amazon, Ebay. Google too, because it provides high value added features to the contact and company modules or custom modules that deal with locations.

Top notch idea if it can be implemented.

Thanks, Dominic.

I think the folks at rssbus.com have made this an easier task. Check out the page at http://www.rssbus.com/connectors/.

It shows a set of "connectors" as they refer to these API integrations that they have created for their product. I think this could be our initial short list plus any that may be missing from the top players we've already mentioned.

What do you think?

Neil Aronson
The SoftwareToolman

[DominicW]

Thanks, Dominic.

I think the folks at rssbus.com have made this an easier task. Check out the page at http://www.rssbus.com/connectors/.

It shows a set of "connectors" as they refer to these API integrations that they have created for their product. I think this could be our initial short list plus any that may be missing from the top players we've already mentioned.

What do you think?

Neil Aronson
The SoftwareToolman

Very interesting, it seems like an intuitive project. Since it connects to any data sources (SOAP, REST and then what we would call Web 2.0 which is mostly XML or RSS) and converts it to any data archetype, it could be used as a model for the architecture but I doubt Thomas would want to rely on a third party architecture, not to mention licensing concerns if there are any. TSB is used to generate software which I am sure complicates licensing (something I am glad Thomas has to deal with ;) )

I am just throwing my 2 cents in, I don't know what limitations Thomas has to work in nor do I have anything to do with the programming behind TSB but this is great brainstorming and hopefully he will find some value in it. I would think that as long as there was an object that directly dealt with RSS/XML/ATOM data to start with, Thomas could at least get this off the ground and evaluate as to what level he would want to take it.

Neil, glad you and I could make it seem so easy for Thomas... in fact I am not sure why its not done today! :D Sorry Thomas, I know you REALLY wanted more on your plate.

Dominic

[SoftwareToolman]

Very interesting, it seems like an intuitive project. Since it connects to any data sources (SOAP, REST and then what we would call Web 2.0 which is mostly XML or RSS) and converts it to any data archetype, it could be used as a model for the architecture but I doubt Thomas would want to rely on a third party architecture, not to mention licensing concerns if there are any. TSB is used to generate software which I am sure complicates licensing (something I am glad Thomas has to deal with ;) )

I am just throwing my 2 cents in, I don't know what limitations Thomas has to work in nor do I have anything to do with the programming behind TSB but this is great brainstorming and hopefully he will find some value in it. I would think that as long as there was an object that directly dealt with RSS/XML/ATOM data to start with, Thomas could at least get this off the ground and evaluate as to what level he would want to take it.

Neil, glad you and I could make it seem so easy for Thomas... in fact I am not sure why its not done today! :D Sorry Thomas, I know you REALLY wanted more on your plate.

Dominic

Well, Dominic, I certainly don't want to get Thomas into any sticky licensing situations. But, given that rssbus revolves around a server-based architecture while TSB is designed for standalone Windows apps, I think that there will be enough architectural differences between the two products to prevent any major issues.

Also, I'm sure that once Thomas wraps his brain around rssbuss and adds his own own unique flavor to the final product, it will far surpass and be unrecognizable from rssbuss.

And, yeah - how come you haven't finished this yet Thomas? After all, this is now a long discussion thread. Didn't we give you enough time? :D

Thanks.

Neil Aronson
The SoftwareToolman

[TigerSoftware]

And, yeah - how come you haven't finished this yet Thomas? After all, this is now a long discussion thread. Didn't we give you enough time? :D

Thanks.

Neil Aronson
The SoftwareToolman

HEHE... it seems I have been slacking a little. ;)


Thomas

[SoftwareToolman]

Hi, Thomas:

If you need any more info or if I can help in any way in getting this going please let me know.

Thanks.

Neil Aronson
The SoftwareToolman

[TigerSoftware]

Hi, Thomas:

If you need any more info or if I can help in any way in getting this going please let me know.

Thanks.

Neil Aronson
The SoftwareToolman


Thanks Neil. It will be some time before I can work on it but will definitely look into it.



Thomas

[ClarityFactor]

Well, Dominic, I certainly don't want to get Thomas into any sticky licensing situations. But, given that rssbus revolves around a server-based architecture while TSB is designed for standalone Windows apps, I think that there will be enough architectural differences between the two products to prevent any major issues.

Also, I'm sure that once Thomas wraps his brain around rssbuss and adds his own own unique flavor to the final product, it will far surpass and be unrecognizable from rssbuss.

And, yeah - how come you haven't finished this yet Thomas? After all, this is now a long discussion thread. Didn't we give you enough time? :D

Thanks.

Neil Aronson
The SoftwareToolman

HAHAHA,

Great Thread Guys

Hmmm, that's funny... thought a heard a whipping sounds.

Anyone else...

Thanks for the thread and the laugh...

Mario