Well, since Countly Community Edition is open source we don't offer any SaaS from our server just yet. Countly Cloud will be the SaaS solution and I believe a micro instance won't do any good after the first week :) But a micro instance is powerful enough to host a website or a blog, even to open up your service for private beta.
HN user
onur
AppFog, Heroku[1] and dotCloud[2] are all great
I tried Trello before and I think its pretty lightweight and useful.
Great idea about an upcoming post :)
That's correct, I mentioned it at the beginning of the post
Correlating the data with marketing efforts would be nice and definitely provide more value but the apps we analyzed have little to no marketing budget (although there are some popular ones). This analysis actually shows the importance of marketing and promotion efforts since without them this is how an app ends up.
We will be doing similar analysis in the following weeks and hopefully will provide more detailed insights.
Yeah its just App Store. We didn't really have a chance to bundle such stats for Android apps yet but I'm pretty sure the results will be pretty similar.
The main point of my blog post was to show our positive experience by using something new to build something new. I'm not talking about renewing your existing backend, changing your perfect PHP implementation to Node.js, I'm talking about our story of choosing a platform for our new project and suggesting people out there to be open to trying new platforms according to their needs. I know the feeling, I did the same before. I have used PHP for projects that I had better alternatives for, just because it felt comfortable and hassle-free.
In our case we have tried several other platforms/languages and the best fit was Node.js for us. “Do the research, be a developer not just an X language developer” would probably sum up my whole point.
You can take a look at http://count.ly if you are looking for an open source solution. It has a Node.js + MongoDB server and Android & iOS SDKs. (Yes I'm the developer)
It would be interesting to play with your API since Countly team is composed of all telco professionals :)
Thanks for pointing that out. I'm pretty sure our co-founder/designer Osman knows about this but anyways being unique is always better :)
We have shortage of documentation for now thats for sure. We will be providing more documents about installation on different platforms in the coming days. If you have any problems or questions we will be more than happy to help if you open up a discussion from http://support.count.ly
Thanks, we intend to do so :)
Yea we used flot but its a little bit custom. Its also planned to be released as a patch.
In less than 30 days the version you can see in the demo (http://count.ly/dashboard) will be available together with the SDK that needs to be embedded into your app.
Thanks! Those two features are planned for the next version since most probably they will not be ready for the first release.
Node.js and mongodb. We actually have an API to read the data even our demo uses this. The API will be released together with the whole platform.
Hi guys, for a couple of months we have been working on this mobile analytics platform and we wanted to show it to the community to get feedback, opinions etc. It has a demo for now and will be available in less than a month.
There is some strong competition in this area, espacially Corona, but I can tell from the first look that you guys are in the right direction. Your comunity seems to be growing already which I believe is the most important for a framework like yours.
You can check the access logs of your server. Probably this is caused by a bot crawling your site and you will see the same IP over and over there. But I'm totally assuming you have a site hosted there which has some kind of database dependence and lots of pages to crawl.
You should really try it for once its very exciting to get all the wonderful feedback from HN. You may even end up talking to the founders of some cool startups.
Will definitely give some shape to the service according to the usage patterns. Your motto suggestion looks good =)
It is on purpose. Sharing just one url is not the intention.
Thanks, I always do the same mistake I'll just go and fix it
Thanks a lot for taking the time to write. Domain name does not mean anything its just a spare domain I had in hand (it is actually Turkish and not related). I didn't think this as a service its just a two day thing I coded up. Its quite obvious that there are lots of missing features, I did not even think of a homepage just like you pointed out.
I usually find myself sending a bulk of links to other people about various things (may be a list of jQuery plugins for a certain job) and such a conversation, most of the time in email, is not really convenient. For now this tool is for sharing a temporary bunch of urls in a beautiful and discussable format.
Edit in place is hard to figure out I admit, may be I can show save and cancel buttons there instead of submit on enter. Your collection title is only editable for you just after you land on that page. When you share the url of your collection it is not editable anymore. Snapshot generation has some features missing like flash and javascript support but should cover most of the sites.
Definitely needs a lot, if I have time I will improve this I really enjoyed developing it.
Yup its generated on my server I don't really like the thumbnail generation services
It gives the warning when thumbnail generation failed for some urls and less than 2 urls left for displaying. Actually I did not implement it yet just watching the real time visitors from GA =)
Thanks! You are right about the main page width. I always have this problem because of using a 1920x1080 resolution. Thanks for the suggestions I will hopefully improve this project.
Thanks! Good idea, if delicious api is still working =)
I guess the difference might be the tools they provide to drag and select parts of pages and only save them to read later