(http://tractionengine.co) A small SaaS for publishers/websites that want their direct ad sales automated (window shopping, purchasing, serving). Runs on a subdomain or root of your liking, branding plus). Works with several payment gateways (we no touch your money), allows real time previewing of slots, publishers can customize the look, texts and wording on the site, got an API, plays with DFP etc. Growth so far is strictly word of mouth (hence no attention to the marketing site), caught the attention of some massive publishers hoping on now. Paying customers. 0 hours/week for most weeks. [AngularJS/FatFree/GoLang] About 8/9 months in.
A news aggregator engine in python for anyone to build their news aggregator upon. Scores using social media vitality, hits & age. Example user http://www.topnews.co.zw [Python(flask)] Runs well on Heroku. Work on it here and there (by span of months)
I've had great experiences with voice-over services etc, but I'm a bit hesitant with creative work like logos (most just run through online logo creators). I do earn some[0] though creating small AngularJS directives and services, pays for my Digital Ocean dev box
Fullstack - AngularJS, NodeJS, Python(Flask), PHP and some mobile Java (Android/J2ME). I also design and manage some high-rps REST APIs as well as plugins for them (WP, OC, EDD and the like)
Yup, for RSS there are ways to implement this out of the box. I was thinking more about regular people who don't know or use RSS, people that publishers would like to retain over the course of reporting a developing story. How do you think this could be accomplished?
How about this? I see a lot of breaking news websites (or blogs that post a story whose details they "update as details come in" have no way (ok, maybe I just haven't come across it) of retaining their readers - a way to subscribe to subsequent updates. So that means busy Bob will either completely forget to come back to the story letter or that he will search for the story again and go read on a competing publication.
So maybe a way for people to subscribe to these "developing stories"? An example implementation in WordPress would be that it adds next to the publish button a checkbox for indicating that this is a developing story. On the user end, all such posts show normally but with an email input and relevant messaging informing the user that the article will be updated as details come in and that they can be notified of them.
I don't know if this qualifies, but the 3D industry which I was pretty involved with for a time comes really close. It is just as "closed", in that they are as sure as developers are that what they are doing is something so awesome they wish everyone knew how awesome it is and should be doing it. And most of them find software development to be a lifeless and colour-less pain, well save for the few among them who can code.
Zimbabwean. Bootstrapping couple tech startups (some profitable) here in Africa for way over a year now.
Most (good) devs I know are self-taught. Employment opportunities pushing code are so scarce it's hopeless for most which is why most move out or go into sys admin/networking. The jobs don't pay that good as well but you can strike out well with consulting.
Thanks to the internet Git, SASS, Heroku, AngularJS, Golang, NodeJS, Docker and all other hacker goodness is adopted just as much (by the few willing) so it's not like we're making sites with bash. We also have a few tech podcasts and the occasional meetup.
Just that our communities are much much smaller and far apart that it's like we're not there at all (thanks economy). Good developers are also hard to find because most see no point in developing skills you never get to use. Things are picking up though
That won't make too many people happy, especially considering they're targeting a market that may have never heard of Stripe or aren't technical enough to pick the Stripe fee inclusion. This doesn't strike much confidence either for a more serious investment, from their terms:
Plasso reserves the right at any
time, with or without notice, to
modify or discontinue the
Service, temporarily or
permanently.
But great all around, using this on a project soon
Focus is key definitely, but isn't there elbow room a bit if you build (usually) SaaS products where it addresses some nichey problem so much there isn't much to be done feature-wise save for a few ad campaigns?
Great job you're doing with PostJobFree. From my experience you're right, one startup is more than handful if you need more features to stay competitive. Two? They've been breaking me to little pieces although one is about to reach feature-completeness.
Wow, five. Yeah it's a strain juggling client work and a startup, I decided a few months ago to die of kwashiorkor if that was what it would take for my startup to show me some (revenue) respect - because juggling that with client work was going to kill me anyway
Just go with WordPress then, you've been hinting at it yourself. Given the amount if plugins and themes out there you should be able to find one for each your needs.
Not master a new language, just dabble in an added few. Kill off an hour of bore learning some NodeJS or AngularJS, what's there to lose? If there's nothing to actually be gained. I do this from time to time and the knowledge I picked up later became the deciding competitive advantages for startups I work on.
Talking serious startups (not odd weekend hacks) I started 3.
The first had traction but no revenue (because of market challenges). So I pulled the plug on it and launched #2 to solve that challenge. #2 grew and is I do it full time now, also just launched #3 3 months ago which had revenue and paying customers from day 1. So I'm just about to re-launch #1 again, see if it will fly or die now that there's no revenue-model excuse