2 ms·
Sounds really cool, I'll take a closer look tomorrow- I'd love to hear about the use-cases, if only for my own curiosity. I certainly meant no disrespect, I wa
by e1ven 17y ago
Sounds really cool, I'll take a closer look tomorrow- I'd love to hear about the use-cases, if only for my own curiosity.
I certainly meant no disrespect, I was only trying to make sure I understand what you do, not impugn the service in any way. From what I've seen, building an internal framework out into a public-facing product seems to be the best way to do it; It ensures you're developing for a real need, not an imaginary "average customer"
Your explanation of the market levels, and where you integrate makes a lot of sense, thanks.
It might be helpful to add something to the page about why you're better than the competitors, even if you don't directly name them.
Thanks again for the explanation, and I hope things work out really well for you.
- ytspar 17y agoWe've done a number of internal and client projects. I can name some of the former. We just launched http://RecessApp.com http://RecessApp.com, a SMS paging system iPhone app. We're running http://AntiTow.com http://AntiTow.com, a street-sweeping/towing alert system. We have http://VampireAds.com http://VampireAds.com, an outdoor text-to screen app. There's a list here: http://holmesmobile.com/projects/ http://holmesmobile.com/projects/ Otherwise, we do primarily real-time notifications and mobile marketing. And you're right about the website. This is the kind of feedback we don't otherwise get, so thanks! I'm also pretty terrible at making blog posts or throwing marketing materials into the ether. Much better when there's something tangible to respond to (which I suppose is analogous to your comment on imaginary "average customers"). But do impugn away if need be, though I'm enlivened by the warm reception so far.