I am exploring uber api and i need to found out if such an application can develop which can share rider's revenue with the integrated app on each trip .
No, it is not possible. Check out our affiliate program for more details about earning with the Uber API.
Right, I'm a little confused by the wording of "integrated app", but I'll just link the API endpoints you should take a look at to see if they satisfy what you need for developing your own application. If this isn't helpful, just say so and I or someone else will try and help further.
If you want to look at riders, the best way I can think of is to use the history to get a list of user recent rides and then request a receipt for every request_id in the history.
If you want to look at drivers, you can just look at all earnings that are given to a specific driver.
If someone wants to correct me on better ways to do this, feel free.
EDIT: Dustin knows better than me!
Title pretty much says it all. Blogs are under the same account. Asked this question on Quora with little response.
I'm looking for perhaps a web app, which automates the process. If there isn't anything already out there, I'm ready to build my own web app using Tumblr's API.
Take a look at this post describing for detailed explanation of moving data from one Tumblr to another http://vinylanswer.tumblr.com/post/42009904333/how-to-turn-your-secondary-tumblr-blog-into-your
I help out at a local soup kitchen, and they are wanting to create a website. Most of their criteria are pretty simple, they want to be able to have a calendar, post pictures, and have a blog. However they also want to be able to manage volunteer's. They want to be able to post a event, have a list of jobs that they need volunteer's for that event, and allow people to sign up for the jobs. I would like to base this website on a well known platform like DotNetNuke, WordPress, or Drupal. Before I go and code my own plugin for managing volunteers I decided to see if I could find a platform that already has a module available. So far I have not been able to find anything. Has anybody heard of one or used one in the past? I would appreciate any suggestions.
There's a whole range of ways to do this, but I haven't ever seen a dedicated solution (plugin or otherwise).
On the one hand, a blog could do all that you're asking. Posting pictures and blog entries? That's wordpress all over. Want a calendar? We have a plugin for that. Want to let volunteers sign up for stuff? Let them post comments.
On the other hand, the problem you're describing isn't unique: In my own experience I've wanted the software you describe. May I suggest that, if you have the time, you make something totally awesome for the volunteer community?
Our company, Wired Impact, recently released a plugin called Wired Impact Volunteer Management that provides exactly the functionality you're looking for. You can learn more and download the plugin at https://wordpress.org/plugins/wired-impact-volunteer-management/.
Its quite annoying sometimes when you have no authentic sources to confirm if particular tasks can be done using iPhone Available (Public) APIs. Whats the preferred way of finding it out?.
Shall we go through iPhone documented APIs,
Ask senior developers ( which i dont prefer, you should not depend on others too much and theres no surety about their opinions ).
Mail Apple ( by the way they offer only 2 technical calls/yr :) ,
Any other ideas?
what do u people suggest?
Thanks Guys!
The public APIs are documented on developer.apple.com in the iOS Reference Library.
However, the only absolutely authentic source on whether their use is acceptable is to submit an app and have it reviewed. Apple just added a review board if you with to appeal a review ruling, so that may be the new last word (unless you get the executive staff's attention (e.g. SJ)).
If you wish more facts before submitting an app, there are a few sites which show which types of apps are being accepted and rejected, and if so, for what given reason. However past acceptance of a type of app is not a precedent or guarantee for any future policy.
If you wish to try interpreting their rules and guidelines yourself, they are available as part of the Developer iOS Standard Agreement.
The Developer support people who answer technical question usually cannot answer review or approval questions, except to point you at the proper API documentation. (The reason may be that these are often legal, corporate policy or marketing questions, not technical questions.)
You can look at official review process from Apple here:
https://developer.apple.com/appstore/resources/approval/guidelines.html
Step 1 : Check the API.
Step 2 : If can't find an way in the API (may be you are looking at wrong API), use Google to find out whether it can be done or not.
Step 3 : If you can't be sure using Google, then ask SO.
IMO, Asking Apple is never an option.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm currently trying to build a personal website to create a presence on the web for myself. My plan is to include content such as my resume, any projects that I have done on my own and links to open source projects that I have contributed to, and so on. However, I'm not sure which approach would be better from a perspective of "advertising" myself, since that what this site does, especially since I am a software developer.
Should I use an out-of-the-box system and extend it as needed, with available modules and custom modules where needed or should I custom build a site and all of its features as I need them? Does a custom site look better in the eyes of a potential employer who might visit my site?
I've toyed with this idea in the past but I don't think it's really a good idea for a number of reasons. Firstly, there are a number of places that can take care of most of this without you needing to do the work or maintenance. Just signing up for a linkedIn account for example will allow you to get most of your needs catered for in this regard. You can create your resume there and bio information etc and make it publicly viewable. The other issue with your "own site" is that if you don't update it often, the information gets stale, and worse yet, people have no reason to go back because "nothing has changed" - and that's not much of an advert for you is it?
Now that I've said all that, I'll make another recommendation. Why not start a blog instead?! If you've got decent experience, why not share that. I'd be willing to bet that this will be the best advert for your skills because:
It's always updated (if you post often)
It's not like you're looking for work doing it - but your (future) employer, or their developers will check it out anyway to get a better insight into your character.
Putting something on your resume doesn't mean you can do it. I'm not saying that you'd lie about your skills :-), but there's no argument about your ability when you're writing articles about the stuff, getting comments and feedback, and better yet, learning EVEN MORE about your passions.
Best of all - you can run your blog from your chosen domain and also point to your resume that is stored in linkedIn. Just an idea...
That's my two pennys worth on that - hope it helps you come to a decision!
If you are a web-specific developer I would go with a custom site, but if you focus more on desktop applications or backend technologies, I think an out of the box system would be fine.
A nice looking, default, off the shelf, complete website could be more impressive than a poorly done, broken, tacked together, incomplete website. Perhaps start with something "off the shelf" but nice looking, keep it simple, professional, and then eventually add more custom functionality, style and content. Potential employers may like to see that you are capable of reusing tried and trued solutions instead of trying to create everything from scratch without a good reason. Or you could spend time combining great components into something even better than the sum of the parts, as Jeff Atwood talks about extensively in the Stack Overflow podcasts. Stack Overflow is a good example of writing lots of custom code, but combining that with some of the best Web 2.0 technologies/widgets/etc. into something coherent, instead of trying to prove that they could implement x/y/z from scratch.
(On the other hand, it's really fun to build your own login system, blog, or photo gallery. If you really enjoy it and you want to learn a lot or create something new and different, then go for it!)
Here's what I did (or am currently doing). First, use an out of the box solution to begin with. In my case, I used BlogEngine.NET, which was open source and easy to set up. This allows me to put content on my site as fast as possible. Now, I can continue to use BlogEngine.NET, and skin my site to give it more personality or I can start rolling out my own solution. However, I haven't found a requirement yet that would give me a reason to waste time building my own solution. Odds are you probably won't either.
I don't think it matters if your site is blatantly using a framework or other "generic" solution. The real question is "is it done well, with taste?" If you are using an out of the box solution, you should take the time and pay attention to details when customizing it as if you were creating it from scratch.
Alternatively, if you're looking for a great learning experience and something to spend a lot of your free time on -- write it yourself. But know that you are re-inventing the wheel, and embrace it.
edit
A recent post from 37Signals, Gearheads don't get it, really sums up a good point about not focusing on the technical details, but "content and community".
Reinventing the wheel is not such a great idea when you are building a personal site. Building your own CMS is fun, and to some degree is something to brag about, but not so much features you won't have the time to build and all the security holes that you won't have the time to fix.
It's much better to pick a good, well-established engine, build a custom theme, and contribute a module or two to it: you'll be writing code that you can show off as a code sample and at the same time creating something useful.
Knowing your way around an open source CMS is a good skill in just about any job: when your boss says - hey, we need a three pager site for client/product/person X in 10 hours, you can say - no problem.
For a simpler portfolio site, Wordpress might meet your needs.
You can set up 'static' Wordpress pages for contact information, various portfolios, a resume, etc. This would also give you a blog if you want to do this.
Wordpress does give you the flexibility to "hide" the blogging part of it and use it basically as a simpler CMS. For example, your root URL of example.com could point to a WP static page, while example.com/blog would be the actual blog pages.
If you self-host Wordpress on your own domain (which I really would recommend instead of going through wordpress.com), it should be trivial to set up a few subdomains for extra content. For example, downloads.example.com could host the actual downloads for projects you've developed linked from the Wordpress portfolio pages. Similarly, if you're doing a lot of web work, a subdomain like lab.example.com or samples.example.com could then host various static (or dynamic) pages where you show off sandboxed pages that are not under the control of Wordpress.
Keep in mind though that you'll want to make your page look good. A sloppy looking site can scare away potential clients, even if you are not looking to do any web work for them.
Putting your resume up online somewhere helps, I get a lot of recruitment emails from people who happened on my resume via googling. However I agree with ColinYounger in that you'll probably get more bang for your buck from LinkedIn.
My advice is this - if you want to take the time out to LEARN a CMS or something, to better yourself, then why not make your first project in one be your homepage?
Maybe enlighten us as to the "features" you want to have on a personal homepage? Outside of a link to an HTML resume and perhaps some links to things you like, not sure exactly what the features of a homepage would be...
It really depends on:
a) what services you provide
b) what your skill level is when it comes to web design/development
If you are primarily a web applications developer then running an off the shelf product or using blatantly using DreamWeaver to develop it may not be so smart -- or maybe your clients aren't adept enough to notice?
Likewise if you're primarily a web designer then it is probably a good idea to design your own website.
Just as a side question and following up on my 'ego trip' comment: why would you take anything on the web to be 'true'? IME printed submissions, while not necessarily accurate, tend to be slightly less, erm... exaggerated than web submissions.
Do those responding\viewing ever hire? I wouldn't google for a candidate. I might ego surf for a respondent, but would ignore CVs.
Rounding back to the OP, I would suggest that you need to SHOW what you're good at - participate in Open Source projects and POST on their forums, link to projects you can post details of and generally try to show what a Good Employee you could be. Just telling me that you're good at [insert latest trend here] means diddly.
I have come to see that the best way to advertise yourself is to put quality content out there. If you write about the technology that you have experience in, maybe create a few tutorials, and if you do all that often enough, that shows some authority in your chosen field of work.
This alone is one of the best advertisements. However, you also want to show passion. And online, that can be shown through how meticulously your site is done (it doesn't have to be a super great UI or something), but it should be neat, clean, and professional. It doesn't matter if its out of the box, or custom designed.
Either way, you will have to work hard to make it look good.