![[)roi(]](/forum/data/avatars/m/8/8711.jpg?1563828683){kind=avatar}
Brilliant, I take it this is one of those Rx per day or per month cellular paid services.Close to 1% of SA population subscribed to our servicesGot almost 50m unique msisdns.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
developing for iOS without a mac?
- Thread starter Sodan
- Start date
koeksGHT
Dealer
[)roi(];17693822 said:
R7 p/d, while we follow regulation there are some cool things I couldn't disclose
Lol... Yeah I actively those (cringeworthy) -- but hey we can't be too particular about what people are willing to pay for.R7 p/d, while we follow regulation there are some cool things I couldn't disclose
koeksGHT
Dealer
[)roi(];17693878 said:
At first I felt bad, then I realized it was 100% voluntary, non forced and if you don't read what you accept your own fault.
I have quite a few macs for development.. but recently I've moved back to windows for development for iOS.
If I had to start over today, I would get something like a mac mini. Then a nice windows machine , visual studio and xamarin is free now.
You dev in VS it compiles over the network to the mac mini and then deploys onto your device for testing.
I still think VS is the best IDE, I can dev in C#, Resharper in VS makes life easy.
The only real pain of this whole thing is the slow build and deploy time, can take up to a minute even for a basic app to run.
If I had to start over today, I would get something like a mac mini. Then a nice windows machine , visual studio and xamarin is free now.
You dev in VS it compiles over the network to the mac mini and then deploys onto your device for testing.
I still think VS is the best IDE, I can dev in C#, Resharper in VS makes life easy.
The only real pain of this whole thing is the slow build and deploy time, can take up to a minute even for a basic app to run.
Lol... have seen some of the tactics employed + plus have previously argued with cellular companies re sharing my mobile number this way: it certainly would be less cringeworthy if you had to enter your mobile number to subscribe; + doubt it would stop the target group re "a fool and his money are soon parted".
But I guess that's part of the ploy: driveby signups, even the accidental ones offer a chance at income.
Last edited:
Only if you're set on using C# and Xamarin, but having used both, what you make up for IDE familiarity is lost with debugging and instrumentation.
For C, C++, Objective C++, Objective C and Swift, Xcode on a Mac is the way to go, especially for a new iOS developer.
Last edited:
koeksGHT
Dealer
[)roi(];17693948 said:
Every bill in Kenya they receive a SMS with service details/price, retention is one of the highest there..
So matter in fact the ANC does quite a lot of good for us
Lol... lucky the rat who eats at the corrupt king's table. No offense intendedEvery bill in Kenya they receive a SMS with service details/price, retention is one of the highest there..
So matter in fact the ANC does quite a lot of good for us
koeksGHT
Dealer
Make the best of a bad situation. Hopefully my fibre makes up for it one day[)roi(];17694082 said:Lol... lucky the rat who eats at the corrupt king's table. No offense intended
Lol... sorry about the rodent reference...Make the best of a bad situation. Hopefully my fibre makes up for it one day
All business has it's dirt + at least you're not f..king up the environment. I did a lot of work for some oil majors, so my income is probably more soiled than yours.
$m@Rt@$$
Expert Member
You can develop for iOS with Visual Studio to my knowledge. Altough I think it's still in beta.
Nope, Its been around for quite a while (Xamarin), however build, signing, etc. still happens on a Mac. In practice it's a pain; re you're going to be hitting bugs related to Xamarin and iOS frameworks, and debugging on Xamarin is poor vs. native on a Mac -- Xamarin guys are helpful but its a lot more problem than benefit. Learning a new language is simple in comparison to learning to develop with the frameworks and for an OS.
Last edited:
koeksGHT
Dealer
[)roi(];17694160 said:
The networks are worse than us, OOB, contracts, lies on limits etc
Exactly...
Sodan
Expert Member
Thanks for the suggestions guys. That mac mini at makro is R10k with only 4GB RAM with an HDD. For a dude without moola, I'm rather picky about what I want. Perhaps I should look at an upgradable older mac mini?
One question that hasn't been addressed: is there some adb equivalent that I can use for debugging from a windows/linux machine with a connected iOS device (iPhone/iPad)? My main concern is ease of debugging during development, and the cheapest way to achieve that.
As for IDEs, I've become an IntelliJ fanboy. I hope to be buying their full suite of products soon (work sponsors a premium personal license for IntelliJ, so I wanna do a deal with them where I pay the difference for the full suite).
One question that hasn't been addressed: is there some adb equivalent that I can use for debugging from a windows/linux machine with a connected iOS device (iPhone/iPad)? My main concern is ease of debugging during development, and the cheapest way to achieve that.
As for IDEs, I've become an IntelliJ fanboy. I hope to be buying their full suite of products soon (work sponsors a premium personal license for IntelliJ, so I wanna do a deal with them where I pay the difference for the full suite).
Nope, you need a Mac. All interfacing works via Xcode & iTunes (to be clear you have to download them)
IntelliJ has support for both Objective-C and Swift on OSX, so continuing to use that won't be a problem, except you're going to have to learn to use the Xcode CLI and toolchain for the rest, basically IntelliJ's coverage is good on the editor part, but they naturally haven't duplicated the entire toolchain but they do however provide tie-ins to some of this. Also IntelliJ has added support for Swift on Linux, but in all honesty it's not yet as reliable as the Android you're used to.
As to developing iOS apps natively on Windows and Linux; this won't be possible because the frameworks are only available in OSX: compiled to both OSX X86-64 and iOS ARM64.
Remember it's not the job of IntelliJ, Microsoft or Canonical to build these; if any it's for Apple and there's no value for them?
Apple are however building the Swift Foundation frameworks to work on both Linux + OSX, and the open source community is busy porting this for Windows, Cygwin, etc. but that's only Foundation (threading, file access, etc.), iOS and OSX have a ton of frameworks and there's just no value in porting this + not everything's compatible. Note: Apple will typically only port frameworks that they see a value in; the Linux value for them is on the backend, i.e. that excludes UIKit.
FYI Microsoft did start the WinObjc project to ground up build a lot of these frameworks for Windows, but their goal is to allow iOS Objective-C apps to be compiled in VS to either run unmodified or easily be ported to Windows phone and tablet -- like Apple they're not interested in making it easy the other way around.
Finally: older mac mini is always a good low cost option; but remember on Macs you are limited to upgrading RAM and HDD, so pick a decent CPU. With the newer ones, even that has become a challenge (i.e. more Appliance like). Alternatively you could find an older iMac (better specs than mac mini)
Last edited:
Lookout on what you buy and don't go for something old but cheap.
I had a situation with an old macbook where I couldn't get get my app signed as Xcode had to be updated before I could continue to use it.
I couldn't update Xcode because my version of OSX was too old.
Aaand I couldn't update OSX because the hardware was too old.
So - apple updated xcode, I could no longer sign and publish my app.
Again, it was an old macbook running either Leopard or Snow Leopard.
I had a situation with an old macbook where I couldn't get get my app signed as Xcode had to be updated before I could continue to use it.
I couldn't update Xcode because my version of OSX was too old.
Aaand I couldn't update OSX because the hardware was too old.
So - apple updated xcode, I could no longer sign and publish my app.
Again, it was an old macbook running either Leopard or Snow Leopard.