|
Interesting
|
|
|
|
|
Unless stuff has changed you still need a Mac to do the build because Xamarin just wraps Apple's tool chain.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
You're right. You can develop on Windows, but you still need a Mac to build.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
That makes it a lot less interesting
|
|
|
|
|
There are services that will do the deployment, I forget the name of the one my company uses, that will compile the iOS version of the app for you and submit to Apple store etc.
That way you don't have to have a Mac. BitRise or DevOps I think might be the names or name of what they use.
B
|
|
|
|
|
Now it's interesting again!
This thread is an emotional roller coaster
|
|
|
|
|
The last time I looked into it, you still need the Apple machine to do storyboarding, which I have found to be helpful.
|
|
|
|
|
If MS would maker a XAML Designer on a par with the WinForms designer, the Storyboard would be superfluous. I don't use it. I muddle through with the UI tools provided for Xamarin XAML.
|
|
|
|
|
To clarify, the VS in Windows handles the building on the Mac remotely, so you don't have to build on the Mac yourself. VS even builds it on the Mac, and runs it in an emulator on the Windows machine. All your development, building, and deployment takes place through VS on Windows.
It is only because of Apple's highly proprietary licensing that the Mac is required.
|
|
|
|
|
There are cloud options where you can push your code to build ios for you. For example, we use Ionic and VS but push to a local Mac pc to build. Some folks even use VM's to do that which is fine, only issue we had was when you try to debug on a local device, VM didn't play well with USB.
Was a while ago though.
|
|
|
|
|
You don’t “need” a Mac. You can use a hackintosh running under VMware. If your dev machine has enough memory, you can run the hackintosh on same machine as VS.
Jlo
|
|
|
|
|
|
|
As long as it does not have 'basic' in the name it's ok, that explains why Python is such an overwhelming success
|
|
|
|
|
There'll be a time when people get nauseous when something is prefixed with Py
Customer: "So we're looking for a vNext Basic developer."
Programmer: "Please no."
Customer: "Alright, we could really use someone who knows PyLibrary though."
Programmer: "Not a chance."
Customer: "Perhaps CFamily is your kind of language?"
Programmer: "Keep this up and you'll get some foul language from me."
Customer: "You'd fit right into our Java* team."
Programmer: "My fist would fit right into your face."
Customer: "We have this Language On Rails."
Programmer: *Hits customer in the eye.*
|
|
|
|
|
Maybe the clue is in the title... "Offline web apps"... why not have a look into creating a HTML web app that works offline using local storage? Unless you have an issue with JavaScript, then it might not be such fun.
Then it should work the same on all device types.
|
|
|
|
|
BecauseSander Rossel wrote: I've also read about actual offline web pages, but doing something like clearing your browser history or cookies will mess them up good.
I've also heard not every browser handles it well and not all web pages can be cached.
Of course, if it's the best option I'll use it.
But not before looking into some other alternatives.
|
|
|
|
|
I guess I got bored of reading by that point, my bad. Personally I would probably only go for offline web app if it was a simple one page application. If you make it too good, you risk the danger of being asked to make it do everything the existing app does.
|
|
|
|
|
musefan wrote: you risk the danger of being asked to make it do everything the existing app does Risk the danger of months worth of work and getting paid accordingly?
Where do I sign!?
|
|
|
|
|
Flutter might be worth a look. I'm sure there should be ways to store data locally and sync back later.
|
|
|
|
|
I've heard about that one.
It's worth considering it, thanks
|
|
|
|
|
If they can use their phone, the internet is available. Make it a web app and walk away.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I'd prefer a happy customer who'll come to me for advice and software in the future as well
|
|
|
|
|
What I'm saying is that if they can use their phone, they can use the internet. If they can't use the internet, make a phone app that can be used offline, and that allows the salesman to manually sync up to the web site when his phone can get a signal.
Problem with a phone/tablet app - you need to put it in the appropriate play store for users to download it. That makes it available to everyone on the planet.
The whole thing is a mess, and it sucks to have to deal with this kind of stuff.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
#realJSOP wrote: The whole thing is a mess, and it sucks to have to deal with this kind of stuff. I completely agree with you there
|
|
|
|