EmbeddedRelated.com
Forums
The 2024 Embedded Online Conference

Android & iOS tools

Started by Unknown October 26, 2014
A customer wants both apps in 2 weeks.  Gee, i can barely do Android in two weeks.  iOS is completely new to me.  I can run ADK on Linux.  Are there iOS tools available on Linux?  How about Android Java to iOS obj C translator?  Any good tools i can pickup in less than 2 weeks?

I keep telling them i cannot do iOS in two weeks, but they are tempting me with big checks.  Perhaps enough to buy iMac, iPhone and iPad all together.  But i don't want to learn iAnything.  I would like to stick to Linux if possible.

On 10/26/2014 9:15 AM, edward.ming.lee@gmail.com wrote:
> A customer wants both apps in 2 weeks. Gee, i can barely do Android in two > weeks. iOS is completely new to me. I can run ADK on Linux. Are there iOS > tools available on Linux? How about Android Java to iOS obj C translator? > Any good tools i can pickup in less than 2 weeks? > > I keep telling them i cannot do iOS in two weeks, but they are tempting me > with big checks. Perhaps enough to buy iMac, iPhone and iPad all together. > But i don't want to learn iAnything. I would like to stick to Linux if > possible.
Then walk away from the job. "Big checks" don't exist if you can't produce. (they also suggest a potential willingness of client to "come after you" when you fail to produce!) Let them find someone else. Then, *hope* they come back to you when that other party "fails to produce".
On 26/10/14 16:15, edward.ming.lee@gmail.com wrote:
> A customer wants both apps in 2 weeks. Gee, i can barely do Android in two weeks. iOS is completely new to me. I can run ADK on Linux. Are there iOS tools available on Linux? How about Android Java to iOS obj C translator? Any good tools i can pickup in less than 2 weeks? > > I keep telling them i cannot do iOS in two weeks, but they are tempting me with big checks. Perhaps enough to buy iMac, iPhone and iPad all together. But i don't want to learn iAnything. I would like to stick to Linux if possible.
One of the fine arts of being in business is when to /decline/ to do work. Customers that blow hot very quickly ("ultra important, must have it tomorrow") often blow cold quickly too. You have to be able to cash the cheque. You might like to retain your integrity, and decline work you believe to be impossible; I have done in the past. I suspect there are tools around the (claim to) automatically translate from Android to iOS and vice versa. Alternatively I am sure there are companies with employees skilled in both.
On Sunday, October 26, 2014 9:22:22 AM UTC-7, Tom Gardner wrote:
> On 26/10/14 16:15, edward.ming.lee@gmail.com wrote: > > A customer wants both apps in 2 weeks. Gee, i can barely do Android in two weeks. iOS is completely new to me. I can run ADK on Linux. Are there iOS tools available on Linux? How about Android Java to iOS obj C translator? Any good tools i can pickup in less than 2 weeks? > > > > I keep telling them i cannot do iOS in two weeks, but they are tempting me with big checks. Perhaps enough to buy iMac, iPhone and iPad all together. But i don't want to learn iAnything. I would like to stick to Linux if possible. > > One of the fine arts of being in business is when to /decline/ to do work. > > Customers that blow hot very quickly ("ultra important, must have it tomorrow") often blow cold quickly too. > > You have to be able to cash the cheque. > > You might like to retain your integrity, and decline work you believe to be impossible; I have done in the past. > > I suspect there are tools around the (claim to) automatically translate from Android to iOS and vice versa. Alternatively I am sure there are companies with employees skilled in both.
Yes, we got lots of responses from people/companies claiming to know iOS. But except for the very expensive one, they (the marketing guys) usually don't know what is a BlueTooth socket. I don't have time to explain until my face turns blue and my tooth fall out of my socket.
On Sun, 26 Oct 2014 09:19:04 -0700, Don Y wrote:

> On 10/26/2014 9:15 AM, edward.ming.lee@gmail.com wrote: >> A customer wants both apps in 2 weeks. Gee, i can barely do Android in >> two weeks. iOS is completely new to me. I can run ADK on Linux. Are >> there iOS tools available on Linux? How about Android Java to iOS obj >> C translator? Any good tools i can pickup in less than 2 weeks? >> >> I keep telling them i cannot do iOS in two weeks, but they are tempting >> me with big checks. Perhaps enough to buy iMac, iPhone and iPad all >> together. But i don't want to learn iAnything. I would like to stick >> to Linux if possible. > > Then walk away from the job. "Big checks" don't exist if you can't > produce. > (they also suggest a potential willingness of client to "come after you" > when you fail to produce!) > > Let them find someone else. Then, *hope* they come back to you when > that other party "fails to produce".
+1. You'll establish a reputation of only promising what you can deliver, and you can always get back to them later if you learn to do iOS. OTOH, if you try and fail then you've established a reputation of another sort. -- www.wescottdesign.com
On Sunday, October 26, 2014 1:44:09 PM UTC-7, Tim Wescott wrote:
> On Sun, 26 Oct 2014 09:19:04 -0700, Don Y wrote: > > > On 10/26/2014 9:15 AM, edward.ming.lee@gmail.com wrote: > >> A customer wants both apps in 2 weeks. Gee, i can barely do Android in > >> two weeks. iOS is completely new to me. I can run ADK on Linux. Are > >> there iOS tools available on Linux? How about Android Java to iOS obj > >> C translator? Any good tools i can pickup in less than 2 weeks? > >> > >> I keep telling them i cannot do iOS in two weeks, but they are tempting > >> me with big checks. Perhaps enough to buy iMac, iPhone and iPad all > >> together. But i don't want to learn iAnything. I would like to stick > >> to Linux if possible. > > > > Then walk away from the job. "Big checks" don't exist if you can't > > produce. > > (they also suggest a potential willingness of client to "come after you" > > when you fail to produce!) > > > > Let them find someone else. Then, *hope* they come back to you when > > that other party "fails to produce". > > +1. You'll establish a reputation of only promising what you can > deliver, and you can always get back to them later if you learn to do > iOS. OTOH, if you try and fail then you've established a reputation of > another sort.
I already told them i can't do iOS within such short time. I tried getting them an iOS developer. But many cookie cutter iOS developer can't really do it in such a short time either. As we discussed here before, Android/iOS BlueTooth is relatively new. It would take lots of readings, trials and errors.
On 10/26/2014 1:59 PM, edward.ming.lee@gmail.com wrote:
> On Sunday, October 26, 2014 1:44:09 PM UTC-7, Tim Wescott wrote: >> On Sun, 26 Oct 2014 09:19:04 -0700, Don Y wrote: >> >>> On 10/26/2014 9:15 AM, edward.ming.lee@gmail.com wrote: >>>> A customer wants both apps in 2 weeks. Gee, i can barely do Android >>>> in two weeks. iOS is completely new to me. I can run ADK on Linux. >>>> Are there iOS tools available on Linux? How about Android Java to iOS >>>> obj C translator? Any good tools i can pickup in less than 2 weeks? >>>> >>>> I keep telling them i cannot do iOS in two weeks, but they are >>>> tempting me with big checks. Perhaps enough to buy iMac, iPhone and >>>> iPad all together. But i don't want to learn iAnything. I would like >>>> to stick to Linux if possible. >>> >>> Then walk away from the job. "Big checks" don't exist if you can't >>> produce. (they also suggest a potential willingness of client to "come >>> after you" when you fail to produce!) >>> >>> Let them find someone else. Then, *hope* they come back to you when >>> that other party "fails to produce". >> >> +1. You'll establish a reputation of only promising what you can deliver, >> and you can always get back to them later if you learn to do iOS. OTOH, >> if you try and fail then you've established a reputation of another sort. > > I already told them i can't do iOS within such short time. I tried getting > them an iOS developer. But many cookie cutter iOS developer can't really do > it in such a short time either. As we discussed here before, Android/iOS > BlueTooth is relatively new. It would take lots of readings, trials and > errors.
*THEY* want to make THEIR problem, YOUR problem. Then, they can hound you as to why it's not done yet, why you are late, why it doesn't work, etc. If they were responsible business people, they would want to "set you up to SUCCEED", not FAIL! I.e., if you've told them "I can't do it", they would WANT to find another "supplier" instead of just trying to offload their problem onto your shoulders...
On Sun, 26 Oct 2014 14:39:25 -0700, Don Y wrote:

> On 10/26/2014 1:59 PM, edward.ming.lee@gmail.com wrote: >> On Sunday, October 26, 2014 1:44:09 PM UTC-7, Tim Wescott wrote: >>> On Sun, 26 Oct 2014 09:19:04 -0700, Don Y wrote: >>> >>>> On 10/26/2014 9:15 AM, edward.ming.lee@gmail.com wrote: >>>>> A customer wants both apps in 2 weeks. Gee, i can barely do Android >>>>> in two weeks. iOS is completely new to me. I can run ADK on Linux. >>>>> Are there iOS tools available on Linux? How about Android Java to >>>>> iOS obj C translator? Any good tools i can pickup in less than 2 >>>>> weeks? >>>>> >>>>> I keep telling them i cannot do iOS in two weeks, but they are >>>>> tempting me with big checks. Perhaps enough to buy iMac, iPhone and >>>>> iPad all together. But i don't want to learn iAnything. I would >>>>> like to stick to Linux if possible. >>>> >>>> Then walk away from the job. "Big checks" don't exist if you can't >>>> produce. (they also suggest a potential willingness of client to >>>> "come after you" when you fail to produce!) >>>> >>>> Let them find someone else. Then, *hope* they come back to you when >>>> that other party "fails to produce". >>> >>> +1. You'll establish a reputation of only promising what you can >>> deliver, >>> and you can always get back to them later if you learn to do iOS. >>> OTOH, if you try and fail then you've established a reputation of >>> another sort. >> >> I already told them i can't do iOS within such short time. I tried >> getting them an iOS developer. But many cookie cutter iOS developer >> can't really do it in such a short time either. As we discussed here >> before, Android/iOS BlueTooth is relatively new. It would take lots of >> readings, trials and errors. > > *THEY* want to make THEIR problem, YOUR problem. Then, they can hound > you as to why it's not done yet, why you are late, why it doesn't work, > etc. > > If they were responsible business people, they would want to "set you up > to SUCCEED", not FAIL! I.e., if you've told them "I can't do it", they > would WANT to find another "supplier" instead of just trying to offload > their problem onto your shoulders...
I'm not sure they're that cynical. They may just be desperate, having been told by multiple vendors that it can't be done, and they're trying in some clumsy way to enable Edward to be their vendor of choice. That doesn't mean that the organization as a whole hasn't evolved into just what you're saying -- on good days, in good organizations, no one of us is as smart as all of us working together. But on bad days, or in bad organizations, no one of us is as dumb as everyone working together. It may just be that sort of organization. Putting aside the fact that my impression is that Android phones and iCrap have both had Bluetooth for just about ever, this is the sort of thing that I'd only do for a customer if it was understood -- in writing, in the contract -- that I'm doing exploration, and that I get paid by hour of effort, not by line item of success. Then if someone tries to bitch beyond canceling the contract in the contractually acceptable manner, particularly if they want to bitch with lawyers, I can just point to the contract, say "I did the work, now pay up". -- Tim Wescott Wescott Design Services http://www.wescottdesign.com
On 10/26/2014 4:52 PM, Tim Wescott wrote:

>>> I already told them i can't do iOS within such short time. I tried >>> getting them an iOS developer. But many cookie cutter iOS developer >>> can't really do it in such a short time either. As we discussed here >>> before, Android/iOS BlueTooth is relatively new. It would take lots of >>> readings, trials and errors. >> >> *THEY* want to make THEIR problem, YOUR problem. Then, they can hound >> you as to why it's not done yet, why you are late, why it doesn't work, >> etc. >> >> If they were responsible business people, they would want to "set you up >> to SUCCEED", not FAIL! I.e., if you've told them "I can't do it", they >> would WANT to find another "supplier" instead of just trying to offload >> their problem onto your shoulders... > > I'm not sure they're that cynical. They may just be desperate, having > been told by multiple vendors that it can't be done, and they're trying in > some clumsy way to enable Edward to be their vendor of choice.
I'm not claiming they're cynical or predatorial. Rather, THEIR tit is in the wringer. They'd much rather it be *yours* and will do/say a lot of irrational things to make that happen: "Yeah, it's OK if that feature isn't present, initially" "Sure, we don't mind if you have to scrap everything and do it ALL over, later, FOR REAL" "We just want something that LOOKS like it works for a dog-and-pony" etc. Later, they forget these "deals with the devil" and are stunned when you claim "finishing the job" will require starting over (etc.) This is especially frustrating when it is the result of a long process during which you have been raising these red flags -- only to have them dismissed, trivially. Until, of course, they all come home to roost and *you* are The Bad Guy (written correspondence can give you the high MORAL ground... but the relationship is shot, regardless!)
 
> Putting aside the fact that my impression is that Android phones and iCrap have both had Bluetooth for just about ever, this is the sort of thing that I'd only do for a customer if it was understood -- in writing, in the contract -- that I'm doing exploration, and that I get paid by hour of effort, not by line item of success.
Bluetooth has been there for audio for a long time, but not for socket API. For Android, it started with 4.3. So, not many people have worked on it and i am not even sure how usable it is. Part of the reason i am taking this job is also my desire to find out if it will really work.

The 2024 Embedded Online Conference